From: Matthew Wilcox <willy@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Matthew Wilcox <willy@debian.org>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [RFC] pci_name()
Date: Thu, 26 Jun 2003 01:53:15 +0100 [thread overview]
Message-ID: <20030626005315.GD451@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030626003620.GB13892@kroah.com>
On Wed, Jun 25, 2003 at 05:36:20PM -0700, Greg KH wrote:
> On Thu, Jun 26, 2003 at 12:35:25AM +0100, Matthew Wilcox wrote:
> >
> > I'd kind of like to get rid of pci_dev->slot_name. It's redundant with
> > pci_dev->dev.bus_id, but that's one hell of a search and replace job.
> > So let me propose pci_name(pci_dev) as a replacement. That has the
>
> That sounds reasonable. But do we really need to do this for 2.6?
>
> Just trying to keep things sane...
I think we really do need to introduce pci_name() for 2.6 (and put it
in 2.4 too). We don't need to eliminate pci_dev->slot_name for 2.6,
but drivers that care need to be able to tell the user which card is
a message is referring to. With overlapping pci bus numbers, the 8
bytes of bus:device.func is no longer unique, so we need to report the
domain number too.
That information's already placed in bus_id, but as I said, I don't
want to start converting all the drivers. We could just make slot_name
larger (Anton posted a patch for this) but I don't want to make pci_dev
even bigger. Having a nice interface like pci_name() makes drivers more
portable between 2.4, 2.6 and 2.8 (as Jeff pointed out).
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-06-26 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 23:35 [RFC] pci_name() Matthew Wilcox
2003-06-26 0:21 ` Jeff Garzik
2003-06-26 0:36 ` Greg KH
2003-06-26 0:53 ` Matthew Wilcox [this message]
2003-06-26 1:02 ` Greg KH
2003-06-26 2:50 ` Matthew Wilcox
2003-06-26 2:52 ` Matthew Wilcox
2003-06-26 11:20 ` Matthew Wilcox
2003-06-26 1:09 ` Anton Blanchard
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=20030626005315.GD451@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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