From: Vasiliy Kulikov <segooon@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: kernel-janitors@vger.kernel.org, Kyle McMartin <kyle@mcmartin.ca>,
Helge Deller <deller@gmx.de>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Frans Pop <elendil@planet.nl>,
Thomas Gleixner <tglx@linutronix.de>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/11] parisc: superio: do not use PCI resources before
Date: Tue, 03 Aug 2010 16:35:08 +0000 [thread overview]
Message-ID: <20100803163508.GA7914@albatros> (raw)
In-Reply-To: <1280851880.2774.36.camel@mulgrave.site>
On Tue, Aug 03, 2010 at 11:11 -0500, James Bottomley wrote:
> On Tue, 2010-08-03 at 19:44 +0400, Kulikov Vasiliy wrote:
> > drivers/parisc/superio.c | 5 +++--
> > 1 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/parisc/superio.c b/drivers/parisc/superio.c
> > index f7806d8..c8a36a2 100644
> > --- a/drivers/parisc/superio.c
> > +++ b/drivers/parisc/superio.c
> > @@ -169,8 +169,6 @@ superio_init(struct pci_dev *pcidev)
> > /* ...then properly fixup the USB to point at suckyio PIC */
> > sio->usb_pdev->irq = superio_fixup_irq(sio->usb_pdev);
> >
> > - printk(KERN_INFO PFX "Found NS87560 Legacy I/O device at %s (IRQ %i)\n",
> > - pci_name(pdev), pdev->irq);
> >
> > pci_read_config_dword (pdev, SIO_SP1BAR, &sio->sp1_base);
> > sio->sp1_base &= ~1;
> > @@ -204,6 +202,9 @@ superio_init(struct pci_dev *pcidev)
> > ret = pci_enable_device(pdev);
> > BUG_ON(ret < 0); /* not too much we can do about this... */
> >
> > + printk(KERN_INFO PFX "Found NS87560 Legacy I/O device at %s (IRQ %i)\n",
> > + pci_name(pdev), pdev->irq);
> > +
> > /*
> > * Next project is programming the onboard interrupt controllers.
> > * PDC hasn't done this for us, since it's using polled I/O.
>
> This really makes no sense; we want the information printed before we
> start all the discovery prints, not after.
Right, I missed it.
> I assume lots of
> initialisers want this too, so it looks particularly silly not to have
> pci_name() returning the correct value until enable time.
>
> If this is just the name initially assigned may change, this definitely
> isn't true for parisc, and even for other things, it would be better to
> print something than nothing.
Not name, but pdev-irq. I was not searching for pci_name() as you can
see in coccinelle script :)
As it is only printing wrong value, the worst case is fooling user that
reads logs.
Is it OK to move pci_enable_device() just before this printk()?
>
> James
>
>
next prev parent reply other threads:[~2010-08-03 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:44 [PATCH 07/11] parisc: superio: do not use PCI resources before pci_enable_device() Kulikov Vasiliy
2010-08-03 16:11 ` [PATCH 07/11] parisc: superio: do not use PCI resources before James Bottomley
2010-08-03 16:35 ` Vasiliy Kulikov [this message]
2010-08-03 16:38 ` James Bottomley
2010-08-03 16:36 ` Jesse Barnes
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=20100803163508.GA7914@albatros \
--to=segooon@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--cc=elendil@planet.nl \
--cc=jejb@parisc-linux.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=tglx@linutronix.de \
/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