From: Greg KH <greg@kroah.com>
To: marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: [BK PATCH] PCI Hotplug changes for 2.4.21-pre1
Date: Mon, 16 Dec 2002 15:48:17 -0800 [thread overview]
Message-ID: <20021216234817.GD17214@kroah.com> (raw)
Hi,
Here is an update for the PCI Hotplug core and the PCI ACPI Hotplug
driver. This fixes a problem for ia64 machines, enabling the driver to
now work properly. Thanks go out to Matthew Wilcox for finally fixing
this problem.
Please pull from: bk://linuxusb.bkbits.net/pci_hp-2.4
The raw patches will follow.
thanks,
greg k-h
drivers/hotplug/acpiphp.h | 2
drivers/hotplug/acpiphp_glue.c | 16 --
drivers/hotplug/acpiphp_pci.c | 48 +++----
drivers/hotplug/pci_hotplug.h | 12 +
drivers/hotplug/pci_hotplug_util.c | 223 ++++++++++++++++++++++---------------
5 files changed, 176 insertions(+), 125 deletions(-)
-----
ChangeSet@1.886, 2002-12-16 11:47:08-08:00, willy@debian.org
[PATCH] Convert acpiphp to pci_bus_*() API [2/2]
Convert the acpiphp driver from the pci_*_nodev() API to the pci_bus_*() API.
This patch is relative to 2.4.21-bk.
drivers/hotplug/acpiphp.h | 2 -
drivers/hotplug/acpiphp_glue.c | 16 ++-----------
drivers/hotplug/acpiphp_pci.c | 48 +++++++++++++++++++----------------------
3 files changed, 26 insertions(+), 40 deletions(-)
------
ChangeSet@1.885, 2002-12-16 11:46:55-08:00, willy@debian.org
[PATCH] Add pci_bus_*() API for 2.4 [1/2]
Introduce the pci_bus_(read|write)_config(byte|word|dword) functions from
Linux 2.5. Reimplement the pci_(read|write)_config(byte|word|dword)_nodev
functions as compatibility wrappers.
drivers/hotplug/pci_hotplug.h | 12 +
drivers/hotplug/pci_hotplug_util.c | 223 ++++++++++++++++++++++---------------
2 files changed, 150 insertions(+), 85 deletions(-)
------
next reply other threads:[~2002-12-16 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 23:48 Greg KH [this message]
2002-12-16 23:49 ` [PATCH] " Greg KH
2002-12-16 23:51 ` 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=20021216234817.GD17214@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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
Powered by JetHome