From: "Daisuke Kobayashi (Fujitsu)" <kobayashi.da-06@fujitsu.com>
To: 'Dan Williams' <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "Yasunori Gotou (Fujitsu)" <y-goto@fujitsu.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"mj@ucw.cz" <mj@ucw.cz>
Subject: RE: [PATCH v3 0/3] Display cxl1.1 device link status
Date: Wed, 27 Mar 2024 08:24:01 +0000 [thread overview]
Message-ID: <OSAPR01MB7182CA5212FC869DA4676C86BA342@OSAPR01MB7182.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <66031eca92f5a_4a98a29427@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Dan Williams wrote:
> Kobayashi,Daisuke wrote:
> > Hello.
> >
> > This patch series adds a feature that displays the link status
> > of the CXL1.1 device.
>
> Good write up! One minor feedback going forward is to drop usage of
> "This patch" in a description as that is self evident.
>
> > CXL devices are extensions of PCIe. Therefore, from CXL2.0 onwards,
> > the link status can be output in the same way as traditional PCIe.
> > However, unlike devices from CXL2.0 onwards, CXL1.1 requires a
> > different method to obtain the link status from traditional PCIe.
> > This is because the link status of the CXL1.1 device is not mapped
> > in the configuration space (as per cxl3.0 specification 8.1).
> > Instead, the configuration space containing the link status is mapped
> > to the memory mapped register region (as per cxl3.0 specification 8.2,
> > Table 8-18). Therefore, the current lspci has a problem where it does
> > not display the link status of the CXL1.1 device.
> > This patch solves these issues.
>
> One common way to rewrite a "This patch..." sentence is in "imperative"
> tense, so for example:
>
> "Solve these issues with sysfs attributes to expose the status
> registers hidden in the RCRB."
>
> ...i.e. write the commit log as if the patch is commanding the code to
> change. You can find some more notes about this here:
>
> https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#patch-
> submission-notes
>
> ...but really, this cover letter is higher quality than most, so thanks
> for that!
>
Thank you for your kind feedback.
In the updated patch, I will revise the text and submit it.
> > Kobayashi,Daisuke (3):
> > Add sysfs attribute for CXL 1.1 device link status
> > Remove conditional branch that is not suitable for cxl1.1 devices
> >
> > drivers/cxl/acpi.c | 4 -
> > drivers/cxl/pci.c | 193
> +++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 193 insertions(+), 4 deletions(-)
> >
> > Add function to display cxl1.1 device link status
> >
> > lib/access.c | 29 +++++++++++++++++++++
> > lib/pci.h | 2 ++
> > ls-caps.c | 73
> ++++++++++++++++++++++++++++++++++++++++++++++++
> ++++
> > 3 files changed, 104 insertions(+)
>
> The typical way I handle cases where I am updating the kernel side and
> the user tooling side of a problem is to post the kernel changes and
> then separately post the user changes with a lore link to the kernel
> submission.
>
> For PCI utils I believe you will need to send a separate pull request
> via github once the kernel changes are accepted.
I understand that it’s better to post separately.
After the changes to the kernel are accepted, I will submit a patch to pciutils.
prev parent reply other threads:[~2024-03-27 8:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 8:05 [PATCH v3 0/3] Display cxl1.1 device link status Kobayashi,Daisuke
2024-03-12 8:05 ` [PATCH v3 1/3] Add sysfs attribute for CXL 1.1 " Kobayashi,Daisuke
2024-03-26 19:51 ` Dan Williams
2024-03-28 1:47 ` Daisuke Kobayashi (Fujitsu)
2024-04-03 9:40 ` Daisuke Kobayashi (Fujitsu)
2024-04-05 8:31 ` Daisuke Kobayashi (Fujitsu)
2024-04-08 21:43 ` Dan Williams
2024-04-09 4:55 ` Daisuke Kobayashi (Fujitsu)
2024-04-05 17:25 ` Jonathan Cameron
2024-04-08 21:32 ` Dan Williams
2024-04-09 14:59 ` Bjorn Helgaas
2024-04-09 15:00 ` Bjorn Helgaas
2024-03-12 8:05 ` [PATCH v3 2/3] Remove conditional branch that is not suitable for cxl1.1 devices Kobayashi,Daisuke
2024-03-26 20:00 ` Dan Williams
2024-03-27 8:26 ` Daisuke Kobayashi (Fujitsu)
2024-03-12 8:05 ` [PATCH v3 3/3] Add function to display cxl1.1 device link status Kobayashi,Daisuke
2024-03-26 20:05 ` Dan Williams
2024-03-27 8:27 ` Daisuke Kobayashi (Fujitsu)
2024-03-29 22:23 ` Martin Mareš
2024-03-30 1:15 ` Dan Williams
2024-03-31 1:03 ` Martin Mareš
2024-04-01 17:47 ` Dan Williams
2024-04-02 7:09 ` Daisuke Kobayashi (Fujitsu)
2024-03-25 4:49 ` [PATCH v3 0/3] Display " Daisuke Kobayashi (Fujitsu)
2024-03-26 19:15 ` Dan Williams
2024-03-27 8:24 ` Daisuke Kobayashi (Fujitsu) [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=OSAPR01MB7182CA5212FC869DA4676C86BA342@OSAPR01MB7182.jpnprd01.prod.outlook.com \
--to=kobayashi.da-06@fujitsu.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=y-goto@fujitsu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox