From: Dan Williams <dan.j.williams@intel.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
"Dave Jiang" <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [PATCH] testing/cxl: Fix abused pci_bus_read_config_word() on platform device
Date: Mon, 21 Oct 2024 13:43:16 -0700 [thread overview]
Message-ID: <6716bce4c37f1_3ee2294c7@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <627bb352-29dc-457f-a383-0dd399f55ab1@fujitsu.com>
Zhijian Li (Fujitsu) wrote:
> Hey Dan,
>
> Thanks for your review...
>
> I want to confirm with you
[..]
>
> Just to confirm, do you mean add device type check to drivers/cxl/core/cdat.c
>
> --- a/drivers/cxl/core/cdat.c
> +++ b/drivers/cxl/core/cdat.c
> @@ -5,6 +5,7 @@
> #include <linux/fw_table.h>
> #include <linux/node.h>
> #include <linux/overflow.h>
> +#include <linux/platform_device.h>
> #include "cxlpci.h"
> #include "cxlmem.h"
> #include "core.h"
> @@ -641,9 +642,13 @@ static int cxl_endpoint_gather_bandwidth(struct cxl_region *cxlr,
> void *ptr;
> int rc;
>
> + if (dev_is_pci(cxlds->dev))
> + return -ENODEV;
> +
> if (cxlds->rcd)
> return -ENODEV;
>
Yes, this one looks good to me. Place the determination as far out into
a leaf function as possible.
prev parent reply other threads:[~2024-10-21 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 1:52 Li Zhijian
2024-10-16 6:02 ` Huang, Ying
2024-10-18 0:22 ` Alison Schofield
2024-10-18 1:20 ` Dan Williams
2024-10-21 3:35 ` Ira Weiny
2024-10-21 3:43 ` Zhijian Li (Fujitsu)
2024-10-21 20:21 ` Ira Weiny
2024-10-21 20:47 ` Dan Williams
2024-10-21 20:43 ` Dan Williams [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=6716bce4c37f1_3ee2294c7@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=vishal.l.verma@intel.com \
--cc=ying.huang@intel.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
all inboxes | Powered by JetHome®