From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>,
Kristen Accardi <kristen.c.accardi@intel.com>,
pcihpd-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org, rajesh.shah@intel.com
Subject: Re: [PATCH] use bus_slot number for name
Date: Fri, 5 Aug 2005 14:33:16 -0700 [thread overview]
Message-ID: <20050805213316.GA3239@kroah.com> (raw)
In-Reply-To: <20050805195123.GN2241@redhat.com>
On Fri, Aug 05, 2005 at 03:51:23PM -0400, Dave Jones wrote:
> On Fri, Aug 05, 2005 at 12:16:06PM -0700, Kristen Accardi wrote:
> > For systems with multiple hotplug controllers, you need to use more than
> > just the slot number to uniquely name the slot. Without a unique slot
> > name, the pci_hp_register() will fail. This patch adds the bus number
> > to the name.
> >
> > Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
> >
> > diff -uprN -X linux-2.6.13-rc4/Documentation/dontdiff linux-2.6.13-rc4/drivers/pci/hotplug/pciehp.h linux-2.6.13-rc4-shpchp-slot-name-fix/drivers/pci/hotplug/pciehp.h
> > --- linux-2.6.13-rc4/drivers/pci/hotplug/pciehp.h 2005-07-28 15:44:44.000000000 -0700
> > +++ linux-2.6.13-rc4-shpchp-slot-name-fix/drivers/pci/hotplug/pciehp.h 2005-08-04 17:57:18.000000000 -0700
> > @@ -302,7 +302,7 @@ static inline void return_resource(struc
> >
> > static inline void make_slot_name(char *buffer, int buffer_size, struct slot *slot)
> > {
> > - snprintf(buffer, buffer_size, "%d", slot->number);
> > + snprintf(buffer, buffer_size, "%04d_%04d", slot->bus, slot->number);
> > }
>
> Won't using..
>
> snprintf(buffer, buffer_size, "%s", pci_name(slot));
As Kristen already said, a slot could refer to multiple pci_dev devices,
so I don't know how well this would really work out.
Although you might want to put the domain in that name, if known, as
large boxes might need that, right?
thanks,
greg k-h
next prev parent reply other threads:[~2005-08-05 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 19:16 [PATCH] use bus_slot number for name Kristen Accardi
2005-08-05 19:51 ` Dave Jones
2005-08-05 20:47 ` Kristen Accardi
2005-08-05 21:31 ` Kristen Accardi
2005-08-05 22:11 ` [Pcihpd-discuss] " Greg KH
2005-08-05 21:33 ` Greg KH [this message]
2005-08-10 15:01 ` [Pcihpd-discuss] " Matthew Wilcox
2005-08-16 22:47 ` Kristen Accardi
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=20050805213316.GA3239@kroah.com \
--to=greg@kroah.com \
--cc=davej@redhat.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@intel.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