From: Greg KH <gregkh@suse.de>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] PCI: make pci_name use dev_name
Date: Wed, 2 Jul 2008 09:04:22 -0700 [thread overview]
Message-ID: <20080702160422.GA2655@suse.de> (raw)
In-Reply-To: <200807020858.20881.jbarnes@virtuousgeek.org>
On Wed, Jul 02, 2008 at 08:58:20AM -0700, Jesse Barnes wrote:
> On Wednesday, July 02, 2008 8:51 am Greg Kroah-Hartman wrote:
> > On Wed, Jul 02, 2008 at 08:35:24AM -0700, Greg Kroah-Hartman wrote:
> > > From: Greg Kroah-Hartman <gregkh@suse.de>
> > >
> > > Also fixes up the sparc PCI code that was assuming this is not a
> > > constant.
> > >
> > > This is done in anticipation of removing the bus_id field from struct
> > > driver.
> > >
> > > Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > >
> > > ---
> > > arch/sparc64/kernel/pci.c | 2 +-
> > > include/linux/pci.h | 4 ++--
> > > 2 files changed, 3 insertions(+), 3 deletions(-)
> > >
> > > --- a/arch/sparc64/kernel/pci.c
> > > +++ b/arch/sparc64/kernel/pci.c
> > > @@ -408,7 +408,7 @@ struct pci_dev *of_create_pci_dev(struct
> > > dev->class = class >> 8;
> > > dev->revision = class & 0xff;
> > >
> > > - sprintf(pci_name(dev), "%04x:%02x:%02x.%d", pci_domain_nr(bus),
> > > + sprintf(dev->dev.bus_id, "%04x:%02x:%02x.%d", pci_domain_nr(bus),
> > > dev->bus->number, PCI_SLOT(devfn), PCI_FUNC(devfn));
> > >
> > > if (ofpci_verbose)
> > > --- a/include/linux/pci.h
> > > +++ b/include/linux/pci.h
> > > @@ -977,9 +977,9 @@ static inline void pci_set_drvdata(struc
> > > /* If you want to know what to call your pci_dev, ask this function.
> > > * Again, it's a wrapper around the generic device.
> > > */
> > > -static inline char *pci_name(struct pci_dev *pdev)
> > > +static inline const char *pci_name(struct pci_dev *pdev)
> >
> > Andrew just pointed out to me that this causes a bunch of compiler
> > warnings to be generated. I'll go audit the tree to fix them as well
> > and send you a follow-on patch if that's ok.
>
> Yeah, works for me. I've got at least one other patch along these lines
> already. Assuming Dave doesn't want to handle these SPARC PCI patches
> anyway...
Well, it's only used in 837 different places, so it might take me a few
hours to ensure I catch all the usages :(
thanks,
greg k-h
next prev parent reply other threads:[~2008-07-02 16:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 15:35 [PATCH] PCI: make pci_name use dev_name Greg Kroah-Hartman
2008-07-02 15:51 ` Greg Kroah-Hartman
2008-07-02 15:58 ` Jesse Barnes
2008-07-02 16:04 ` Greg KH [this message]
2008-07-02 20:22 ` Greg KH
2008-07-02 20:24 ` [patch 01/04] MTD: handle pci_name() being const Greg Kroah-Hartman
2008-07-02 20:24 ` [patch 02/04] PCI: " Greg Kroah-Hartman
2008-07-03 19:33 ` Jesse Barnes
2008-07-02 20:24 ` [patch 03/04] 3c59x: " Greg Kroah-Hartman
2008-07-02 23:28 ` Andrew Morton
2008-07-03 12:17 ` Steffen Klassert
2008-07-03 15:43 ` Greg KH
2008-08-07 6:31 ` Jeff Garzik
2008-08-07 10:18 ` Steffen Klassert
2008-07-02 20:24 ` [patch 04/04] USB: " Greg Kroah-Hartman
2008-07-03 19:37 ` [PATCH] PCI: make pci_name use dev_name Jesse Barnes
2008-07-03 20:24 ` Greg KH
2008-07-03 20:33 ` Jesse Barnes
2008-07-03 20:52 ` Greg KH
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=20080702160422.GA2655@suse.de \
--to=gregkh@suse.de \
--cc=davem@davemloft.net \
--cc=jbarnes@virtuousgeek.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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