Any change and question relevant to should also CC to the CXL mailing list.
Reviewed-by: Dave Jiang <[email protected]> Signed-off-by: Li Zhijian <[email protected]> --- V2: add reviewed tag --- CONTRIBUTING.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4f4865db9da4..7d1e7f64984f 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 + **```[email protected]```**. + 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 - **```[email protected]```** - An archive is available on [lore](https://lore.kernel.org/nvdimm/) + **```[email protected]```** and CC **```[email protected]```** 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:[email protected]) the above list. + [email](mailto:[email protected]) the above list and CC + `linux-cxl@[email protected]` if needed. 1. We follow the Linux Kernel [Coding Style Guide][cs] as applicable. -- 2.29.2
