From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Philipp Stanner <pstanner@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] PCI: Improve printout in pdev_sort_resources()
Date: Thu, 17 Oct 2024 14:35:55 +0300 (EEST) [thread overview]
Message-ID: <8b9f3fab-bfeb-5aa7-fc6a-26b9faa89417@linux.intel.com> (raw)
In-Reply-To: <20241017121203.000003d8@Huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
On Thu, 17 Oct 2024, Jonathan Cameron wrote:
> On Thu, 17 Oct 2024 12:55:45 +0300
> Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> wrote:
>
> > Use pci_resource_name() helper in pdev_sort_resources() to print
> > resources in user-friendly format. Also replace the vague "bogus
> > alignment" with a more precise explanation of the problem.
> >
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > ---
> >
> > v2:
> > - Place colon after %s %pR to be consistent with other printouts
> > - Replace vague "bogus alignment" with the exact cause
> >
> > drivers/pci/setup-bus.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> > index 23082bc0ca37..0fd286f79674 100644
> > --- a/drivers/pci/setup-bus.c
> > +++ b/drivers/pci/setup-bus.c
> > @@ -134,6 +134,7 @@ static void pdev_sort_resources(struct pci_dev *dev, struct list_head *head)
> > int i;
> >
> > pci_dev_for_each_resource(dev, r, i) {
> > + const char *r_name = pci_resource_name(dev, i);
> > struct pci_dev_resource *dev_res, *tmp;
> > resource_size_t r_align;
> > struct list_head *n;
> > @@ -146,8 +147,8 @@ static void pdev_sort_resources(struct pci_dev *dev, struct list_head *head)
> >
> > r_align = pci_resource_alignment(dev, r);
> > if (!r_align) {
> > - pci_warn(dev, "BAR %d: %pR has bogus alignment\n",
> > - i, r);
> > + pci_warn(dev, "%s %pR: alignment must not be zero\n",
> > + r_name, r);
>
> Why bother with local variable if only used here?
No other reason than it seems to always be a local variable in the other
places too regardless the number of uses.
> Absolutely fine if you have more code coming that uses it again though!
>
> Otherwise seems sensible change.
--
i.
next prev parent reply other threads:[~2024-10-17 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 9:55 [PATCH v2 1/1] PCI: Improve printout in pdev_sort_resources() Ilpo Järvinen
2024-10-17 11:12 ` Jonathan Cameron
2024-10-17 11:35 ` Ilpo Järvinen [this message]
2024-10-17 13:29 ` Jonathan Cameron
2024-10-17 13:49 ` Philipp Stanner
[not found] <20241018234258.GA770341@bhelgaas>
2024-10-21 17:53 ` Bjorn Helgaas
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=8b9f3fab-bfeb-5aa7-fc6a-26b9faa89417@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pstanner@redhat.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