From: Dave Jiang <dave.jiang@intel.com>
To: Li Zhijian <lizhijian@fujitsu.com>, <nvdimm@lists.linux.dev>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: [ndctl PATCH 1/2] CONTRIBUTING.md: document cxl mailing list
Date: Thu, 25 May 2023 08:29:14 -0700 [thread overview]
Message-ID: <b87e4a68-d58d-03ba-539d-7e2b9e7530be@intel.com> (raw)
In-Reply-To: <20230523035704.826188-1-lizhijian@fujitsu.com>
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.
>
prev parent reply other threads:[~2023-05-25 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 3:57 [ndctl PATCH 1/2] CONTRIBUTING.md: document cxl mailing list Li Zhijian
2023-05-23 3:57 ` [ndctl PATCH 2/2] README.md: document CXL unit tests Li Zhijian
2023-05-25 15:28 ` Dave Jiang
2023-05-26 4:01 ` Zhijian Li (Fujitsu)
2023-05-26 4:21 ` Zhijian Li (Fujitsu)
2023-05-30 21:38 ` Dave Jiang
2023-05-25 15:29 ` Dave Jiang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b87e4a68-d58d-03ba-539d-7e2b9e7530be@intel.com \
--to=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=nvdimm@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.