diff mbox series

[ndctl,1/2] CONTRIBUTING.md: document cxl mailing list

Message ID 20230523035704.826188-1-lizhijian@fujitsu.com
State Superseded
Headers show
Series [ndctl,1/2] CONTRIBUTING.md: document cxl mailing list | expand

Commit Message

Zhijian Li (Fujitsu) May 23, 2023, 3:57 a.m. UTC
Any change and question relevant to should also CC to the CXL mailing
list.

Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
---
 CONTRIBUTING.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

Comments

Dave Jiang May 25, 2023, 3:29 p.m. UTC | #1
On 5/22/23 20:57, Li Zhijian wrote:
> Any change and question relevant to should also CC to the CXL mailing
> list.
>
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>

Reviewed-by: Dave Jiang <dave.jiang@intel.com>

Thank you for sending this Zhijian!


> ---
>   CONTRIBUTING.md | 12 +++++++++---
>   1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
> index 4f4865db9da4..c5eb391122d5 100644
> --- a/CONTRIBUTING.md
> +++ b/CONTRIBUTING.md
> @@ -5,15 +5,21 @@ Thank you for taking the time to contribute to ndctl.
>   The following is a set of guidelines that we adhere to, and request that
>   contributors follow.
>   
> +1. **NOTE**: ndctl utils have extended to support CXL CLI, so any change
> +   and question relevant to CXL should also CC to the CXL mailing list
> +   **```linux-cxl@vger.kernel.org```**.
> +
>   1. The libnvdimm (kernel subsystem) and ndctl developers primarily use
>      the [nvdimm](https://subspace.kernel.org/lists.linux.dev.html)
>      mailing list for everything. It is recommended to send patches to
> -   **```nvdimm@lists.linux.dev```**
> -   An archive is available on [lore](https://lore.kernel.org/nvdimm/)
> +   **```nvdimm@lists.linux.dev```** and CC **```linux-cxl@vger.kernel.org```** if needed.
> +   The archives are available on [nvdimm](https://lore.kernel.org/nvdimm/) and
> +   [cxl](https://lore.kernel.org/linux-cxl/)
>   
>   1. Github [issues](https://github.com/pmem/ndctl/issues) are an acceptable
>      way to report a problem, but if you just have a question,
> -   [email](mailto:nvdimm@lists.linux.dev) the above list.
> +   [email](mailto:nvdimm@lists.linux.dev) the above list and CC `linux-cxl@linux-cxl@vger.kernel.org`
> +   if needed.
>   
>   1. We follow the Linux Kernel [Coding Style Guide][cs] as applicable.
>
diff mbox series

Patch

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4f4865db9da4..c5eb391122d5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -5,15 +5,21 @@  Thank you for taking the time to contribute to ndctl.
 The following is a set of guidelines that we adhere to, and request that
 contributors follow.
 
+1. **NOTE**: ndctl utils have extended to support CXL CLI, so any change
+   and question relevant to CXL should also CC to the CXL mailing list
+   **```linux-cxl@vger.kernel.org```**.
+
 1. The libnvdimm (kernel subsystem) and ndctl developers primarily use
    the [nvdimm](https://subspace.kernel.org/lists.linux.dev.html)
    mailing list for everything. It is recommended to send patches to
-   **```nvdimm@lists.linux.dev```**
-   An archive is available on [lore](https://lore.kernel.org/nvdimm/)
+   **```nvdimm@lists.linux.dev```** and CC **```linux-cxl@vger.kernel.org```** if needed.
+   The archives are available on [nvdimm](https://lore.kernel.org/nvdimm/) and
+   [cxl](https://lore.kernel.org/linux-cxl/)
 
 1. Github [issues](https://github.com/pmem/ndctl/issues) are an acceptable
    way to report a problem, but if you just have a question,
-   [email](mailto:nvdimm@lists.linux.dev) the above list.
+   [email](mailto:nvdimm@lists.linux.dev) the above list and CC `linux-cxl@linux-cxl@vger.kernel.org`
+   if needed.
 
 1. We follow the Linux Kernel [Coding Style Guide][cs] as applicable.