public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
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: Thu, 26 Jun 2003 12:20:32 +0100	[thread overview]
Message-ID: <20030626112032.GK451@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030626025057.GE451@parcelfarce.linux.theplanet.co.uk>

On Thu, Jun 26, 2003 at 03:50:57AM +0100, Matthew Wilcox wrote:
> This patch introduces pci_name() and converts slot_name into a pointer to
> dev.bus_id.

Here's the compatibility patch for 2.4:

--- linux/include/linux/pci.h	2003-05-21 05:21:29.000000000 -0400
+++ linux-acpi/include/linux/pci.h	2003-06-26 06:39:58.000000000 -0400
@@ -773,6 +773,11 @@
 	pdev->driver_data = data;
 }
 
+static inline char *pci_name(struct pci_dev *pdev)
+{
+	return pdev->slot_name;
+}
+
 /*
  *  The world is not perfect and supplies us with broken PCI devices.
  *  For at least a part of these bugs we need a work-around, so both

-- 
"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

  parent reply	other threads:[~2003-06-26 11:06 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
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 [this message]
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=20030626112032.GK451@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