All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [BK PATCH] More PCI fixes for 2.6.0-test2
Date: Fri, 8 Aug 2003 17:30:36 -0700	[thread overview]
Message-ID: <20030809003036.GA3163@kroah.com> (raw)

Hi,

Here are a few more fixes for the PCI core code for 2.6.0-test2-bk.
I've removed all of the struct device.name usages as that field is about
to go away, and there is a fix from Ivan in here too.

Please pull from:
	bk://kernel.bkbits.net/gregkh/linux/pci-2.6

thanks,

greg k-h

p.s. I'll send these as patches in response to this email to lkml for
those who want to see them.


 drivers/char/agp/hp-agp.c |    2 +-
 drivers/net/eepro100.c    |    2 +-
 drivers/pci/names.c       |    2 +-
 drivers/pci/pci.c         |    2 +-
 drivers/pci/pci.ids       |    3 ++-
 drivers/pci/probe.c       |    9 +++------
 drivers/pci/proc.c        |    7 ++++++-
 drivers/pci/quirks.c      |    2 +-
 drivers/pci/setup-bus.c   |    6 ++++--
 drivers/pci/setup-res.c   |    2 +-
 include/linux/pci.h       |    3 +++
 include/linux/pci_ids.h   |    3 ++-
 12 files changed, 26 insertions(+), 17 deletions(-)
-----

Alex Williamson:
  o PCI: trivial 2.4/2.6 PCI name change/addition

Greg Kroah-Hartman:
  o PCI: make eepro100 driver use pci_name() instead of dev.name
  o PCI: remove all struct device.name usage from the PCI core code

Ivan Kokshaysky:
  o PCI: pci_enable_device vs bridges bugs


             reply	other threads:[~2003-08-09  0:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09  0:30 Greg KH [this message]
2003-08-09  0:32 ` [PATCH] More PCI fixes for 2.6.0-test2 Greg KH
2003-08-09  0:32   ` Greg KH
2003-08-09  0:32     ` Greg KH
2003-08-09  0:32       ` Greg KH
2003-08-09  8:15 ` [BK PATCH] " Russell King
2003-08-09 17:07   ` 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=20030809003036.GA3163@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.