mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Philipp Stanner <pstanner@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,  LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] PCI: Convert pdev_sort_resources() to use resource name helper
Date: Wed, 16 Oct 2024 16:15:43 +0300 (EEST)	[thread overview]
Message-ID: <fc0649b5-d065-2627-f475-d61f0594d0e5@linux.intel.com> (raw)
In-Reply-To: <1cf314b3e91779e3353bbcaf8ad13516a00642e3.camel@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]

On Wed, 16 Oct 2024, Philipp Stanner wrote:

> On Wed, 2024-10-16 at 15:00 +0300, Ilpo Järvinen wrote:
> > Use pci_resource_name() helper in pdev_sort_resources() to print
> > resources in user-friendly format.
> > 
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > ---
> >  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..071c5436b4a5 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 has bogus
> > alignment\n",
> > +				 r_name, r);
> 
> Why do you remove the BAR index number, don't you think this
> information is also useful?

That's because of how pci_resource_name() works. The number will be 
included in the returned string and it won't be always same as i.
So that change is done on purpose.

> One could also consider printing r_align, would that be useful?

As per the preceeding condition, it's known to be zero so it's not 
that useful for any developer looking at these code lines.

> Note
> that there is a similar pci_warn down below in line 1118 that does
> print it. Would you want to change that pci_warn()-string, too?

pci_warn() on line 1118 does NOT print i (as expected when using 
pci_resource_name()) and there align is not zero so I don't see how this 
is relevant.

But thanks for taking a look anyway. :-)

-- 
 i.

  reply	other threads:[~2024-10-16 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 12:00 Ilpo Järvinen
2024-10-16 13:05 ` Philipp Stanner
2024-10-16 13:15   ` Ilpo Järvinen [this message]
2024-10-16 13:19     ` Ilpo Järvinen
2024-10-16 13:21     ` Philipp Stanner
2024-10-16 13:34       ` Ilpo Järvinen

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=fc0649b5-d065-2627-f475-d61f0594d0e5@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.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

all inboxes | Powered by JetHome®