public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [BK PATCH] PCI fixes for 2.6.7
Date: Thu, 24 Jun 2004 14:30:29 -0700	[thread overview]
Message-ID: <20040624213029.GA2477@kroah.com> (raw)

Hi,

Here are some small PCI patches for 2.6.7.  They include some pci id
fixes, quirk fixups, and pci hotplug driver updates.  They have all been
in the last few -mm releases.

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.


 Documentation/pci.txt                  |    5 
 Documentation/power/pci.txt            |    8 
 arch/i386/kernel/dmi_scan.c            |   59 +++++
 arch/i386/pci/irq.c                    |   27 ++
 drivers/pci/hotplug/pciehp_ctrl.c      |  147 ++++----------
 drivers/pci/hotplug/pciehp_hpc.c       |    4 
 drivers/pci/hotplug/pciehprm_acpi.c    |   22 +-
 drivers/pci/hotplug/pciehprm_nonacpi.c |   18 +
 drivers/pci/hotplug/rpadlpar_core.c    |   28 --
 drivers/pci/hotplug/rpaphp.h           |   28 ++
 drivers/pci/hotplug/rpaphp_core.c      |  199 +++++++++++++-------
 drivers/pci/hotplug/rpaphp_pci.c       |  328 ++++++++++++++++++++++-----------
 drivers/pci/hotplug/rpaphp_slot.c      |  136 +++++++++++--
 drivers/pci/hotplug/rpaphp_vio.c       |    6 
 drivers/pci/hotplug/shpchp.h           |    1 
 drivers/pci/hotplug/shpchp_ctrl.c      |   60 ++----
 drivers/pci/hotplug/shpchp_pci.c       |    1 
 drivers/pci/hotplug/shpchprm_acpi.c    |   22 +-
 drivers/pci/hotplug/shpchprm_nonacpi.c |   18 +
 drivers/pci/msi.c                      |   10 -
 drivers/pci/pci.c                      |    2 
 drivers/pci/quirks.c                   |    1 
 include/linux/pci_ids.h                |   54 +++--
 23 files changed, 781 insertions(+), 403 deletions(-)
-----

<ossi:kde.org>:
  o PCI: (one more) PCI quirk for SMBus bridge on Asus P4 boards

Bjorn Helgaas:
  o PCI: clarify pci.txt wrt IRQ allocation

Daniel Ritz:
  o PCI: fix irq routing on acer travelmate 360 laptop

Dely Sy:
  o Fixes for hot-plug drivers (updated)

Linda Xie:
  o PCI Hotplug: rpaphp.patch -- multi-function devices not handled correctly

Roger Luethi:
  o PCI: Fix off-by-one in pci_enable_wake
  o PCI: Fix PME bits in pci.txt

Roland Dreier:
  o PCI: Fix MSI-X setup

Stephen Hemminger:
  o PCI: add id's for sk98 driver
  o PCI: fix out of order entry in pci_ids.h
  o PCI: remove duplicate in pci_ids.h


             reply	other threads:[~2004-06-24 21:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 21:30 Greg KH [this message]
2004-06-24 21:46 ` [PATCH] PCI fixes for 2.6.7 Greg KH
2004-06-24 21:46   ` Greg KH
2004-06-24 21:46     ` Greg KH
2004-06-24 21:46       ` Greg KH
2004-06-24 21:46         ` Greg KH
2004-06-24 21:46           ` Greg KH
2004-06-24 21:46             ` Greg KH
2004-06-24 21:46               ` Greg KH
2004-06-24 21:46                 ` Greg KH
2004-06-24 21:46                   ` Greg KH
2004-06-24 21:46                     ` 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=20040624213029.GA2477@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox