From: Robert Richter <rrichter@amd.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Robert Richter <rric@kernel.org>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 1/3] cxl/mem: Quiet port walking warning
Date: Wed, 4 Jan 2023 10:36:13 +0100 [thread overview]
Message-ID: <Y7VIjfnd957nCncQ@rric.localdomain> (raw)
In-Reply-To: <63b49906246a_5174129457@dwillia2-xfh.jf.intel.com.notmuch>
On 03.01.23 13:07:18, Dan Williams wrote:
> Robert Richter wrote:
> > On 16.12.22 17:33:32, Dan Williams wrote:
> > > diff --git a/drivers/cxl/core/port.c b/drivers/cxl/core/port.c
> > > index 810e60cc331c..6296d2bc909a 100644
> > > --- a/drivers/cxl/core/port.c
> > > +++ b/drivers/cxl/core/port.c
> > > @@ -1400,8 +1400,8 @@ int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd)
> > >
> > > uport_dev = dport_dev->parent;
> > > if (!uport_dev) {
> > > - dev_warn(dev, "at %s no parent for dport: %s\n",
> > > - dev_name(iter), dev_name(dport_dev));
> > > + dev_dbg(dev, "at %s no parent for dport: %s\n",
> > > + dev_name(iter), dev_name(dport_dev));
> > > return -ENXIO;
> >
> > Maybe we should also change the return code to the common -EAGAIN for
> > this case here too? It looks like it is just passed to
> > cxl_mem_probe(), so there are probably no side effects of this change.
> > The probe is triggered then again by the base driver.
>
> Good point, might as well explicitly return EPROBE_DEFER rather than let
> the driver core turn EAGAIN into EPROBE_DEFER. Tests seem to pass with
> that change as well.
Yes, EPROBE_DEFER is the one used in the Deferred Probe
infrastructure.
Thanks,
-Robert
next prev parent reply other threads:[~2023-01-04 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 1:33 [PATCH 0/3] cxl: Misc fixups that missed v6.2 Dan Williams
2022-12-17 1:33 ` [PATCH 1/3] cxl/mem: Quiet port walking warning Dan Williams
2023-01-03 10:49 ` Robert Richter
2023-01-03 21:07 ` Dan Williams
2023-01-04 9:36 ` Robert Richter [this message]
2023-01-13 11:04 ` Jonathan Cameron
2023-01-25 21:09 ` Dan Williams
2023-01-25 22:11 ` [PATCH v2 1/3] cxl/mem: Quiet port walking warnings Dan Williams
2023-01-26 10:02 ` Jonathan Cameron
2023-01-26 11:47 ` Robert Richter
2022-12-17 1:33 ` [PATCH 2/3] cxl/region: Clarify when a cxld->commit() callback is mandatory Dan Williams
2023-01-13 11:24 ` Jonathan Cameron
2023-01-25 22:44 ` Dan Williams
2022-12-17 1:33 ` [PATCH 3/3] cxl/port: Link the 'parent_dport' in portX/ and endpointX/ sysfs Dan Williams
2023-01-13 11:39 ` Jonathan Cameron
2023-01-25 22:46 ` Dan Williams
2023-01-25 23:32 ` Dan Williams
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=Y7VIjfnd957nCncQ@rric.localdomain \
--to=rrichter@amd.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rric@kernel.org \
/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