From: Dave Jiang <dave.jiang@intel.com>
To: "Kobayashi,Daisuke" <kobayashi.da-06@fujitsu.com>,
kobayashi.da-06@jp.fujitsu.com, linux-cxl@vger.kernel.org
Cc: y-goto@fujitsu.com, linux-pci@vger.kernel.org, mj@ucw.cz,
dan.j.williams@intel.com
Subject: Re: [PATCH v4 1/3] cxl: Add rcd_regs to cxl_rcrb_info
Date: Tue, 9 Apr 2024 12:08:07 -0700 [thread overview]
Message-ID: <84c52acf-54af-4370-983d-e03c92564774@intel.com> (raw)
In-Reply-To: <20240409073528.13214-2-kobayashi.da-06@fujitsu.com>
On 4/9/24 12:35 AM, Kobayashi,Daisuke wrote:
> Add rcd regs to cxl_rcrb_info to cache the RCD register values.
I suggest you squash this patch with 2/3. There's not much meaning of adding variables without showing usage.
>
> Signed-off-by: "Kobayashi,Daisuke" <kobayashi.da-06@fujitsu.com>
> ---
> drivers/cxl/cxl.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> index 003feebab79b..2dc827c301a1 100644
> --- a/drivers/cxl/cxl.h
> +++ b/drivers/cxl/cxl.h
> @@ -647,6 +647,9 @@ cxl_find_dport_by_dev(struct cxl_port *port, const struct device *dport_dev)
> struct cxl_rcrb_info {
> resource_size_t base;
> u16 aer_cap;
> + u16 rcd_lnkctrl;
> + u16 rcd_lnkstatus;
> + u32 rcd_lnkcap;
> };
>
> /**
next prev parent reply other threads:[~2024-04-09 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 7:35 [PATCH v4 0/3] cxl: Export cxl1.1 device link status to sysfs Kobayashi,Daisuke
2024-04-09 7:35 ` [PATCH v4 1/3] cxl: Add rcd_regs to cxl_rcrb_info Kobayashi,Daisuke
2024-04-09 19:08 ` Dave Jiang [this message]
2024-04-09 7:35 ` [PATCH v4 2/3] cxl/core/regs: Add rcd_regs initialization at __rcrb_to_component() Kobayashi,Daisuke
2024-04-09 19:15 ` Dave Jiang
2024-04-10 7:14 ` Daisuke Kobayashi (Fujitsu)
2024-04-09 7:35 ` [PATCH v4 3/3] cxl/pci: Add sysfs attribute for CXL 1.1 device link status Kobayashi,Daisuke
2024-04-09 15:05 ` Bjorn Helgaas
2024-04-09 18:04 ` Dan Williams
2024-04-09 22:18 ` Lukas Wunner
2024-04-09 21:33 ` Dan Williams
2024-04-09 21:47 ` Dan Williams
2024-04-10 7:22 ` Daisuke Kobayashi (Fujitsu)
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=84c52acf-54af-4370-983d-e03c92564774@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=kobayashi.da-06@fujitsu.com \
--cc=kobayashi.da-06@jp.fujitsu.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