From: Greg KH <greg@kroah.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [BK PATCH] PCI Hotplug changes for 2.5.20
Date: Fri, 7 Jun 2002 13:42:28 -0700 [thread overview]
Message-ID: <20020607204227.GA16439@kroah.com> (raw)
Pull from: bk://linuxusb.bkbits.net/pci_hp-2.5
drivers/hotplug/ibmphp_core.c | 6 -
drivers/hotplug/ibmphp_ebda.c | 17 ++--
drivers/hotplug/ibmphp_hpc.c | 131 +++++++++++++++++--------------------
drivers/hotplug/ibmphp_res.c | 15 ++--
drivers/hotplug/pci_hotplug_core.c | 1
5 files changed, 84 insertions(+), 86 deletions(-)
------
ChangeSet@1.468, 2002-06-07 13:32:51-07:00, greg@kroah.com
IBM PCI Hotplug driver: added __init and __exit to functions that needed it.
Thanks to Andrey Panin <pazke@orbita1.ru> for pointing these out to me.
drivers/hotplug/ibmphp_core.c | 4 ++--
drivers/hotplug/ibmphp_ebda.c | 17 +++++++++--------
drivers/hotplug/ibmphp_hpc.c | 17 +++++++++--------
drivers/hotplug/ibmphp_res.c | 15 ++++++++-------
4 files changed, 28 insertions(+), 25 deletions(-)
------
ChangeSet@1.467, 2002-06-07 13:29:15-07:00, greg@kroah.com
PCI Hotplug core: added #include <linux/namei.h> to fix compile time warning
drivers/hotplug/pci_hotplug_core.c | 1 +
1 files changed, 1 insertion(+)
------
ChangeSet@1.466, 2002-06-07 13:27:01-07:00, greg@kroah.com
IBM PCI Hotplug driver: polling thread locking cleanup
removed a lot of bizzare polling locking logic, causing the driver to not sleep
for 2 seconds with some locks held. This improves userspace interaction by
a few orders of magnitude :)
drivers/hotplug/ibmphp_core.c | 2
drivers/hotplug/ibmphp_hpc.c | 114 +++++++++++++++++++-----------------------
2 files changed, 55 insertions(+), 61 deletions(-)
------
reply other threads:[~2002-06-07 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020607204227.GA16439@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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