From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [RFC] pci_name()
Date: Wed, 25 Jun 2003 20:21:47 -0400 [thread overview]
Message-ID: <3EFA3C9B.8030301@pobox.com> (raw)
In-Reply-To: <20030625233525.GB451@parcelfarce.linux.theplanet.co.uk>
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
> benefit of being shorter than either of the others and lets us do fun
> & interesting things later (maybe construct it on the fly for systems
and also it's nicely backwards compatible (source-wise), too.
Jeff
next prev parent reply other threads:[~2003-06-26 0:07 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 [this message]
2003-06-26 0:36 ` Greg KH
2003-06-26 0:53 ` Matthew Wilcox
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=3EFA3C9B.8030301@pobox.com \
--to=jgarzik@pobox.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=willy@debian.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