From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: Re: [BK PATCH] PCI hotplug changes for 2.5.46
Date: Tue, 5 Nov 2002 17:37:08 -0800 [thread overview]
Message-ID: <20021106013708.GR18627@kroah.com> (raw)
In-Reply-To: <20021106013615.GQ18627@kroah.com>
ChangeSet 1.875.1.1, 2002/11/02 22:25:32-08:00, rmk@arm.linux.org.uk
[PATCH] PCI hotplug comment fixes
Fix comments about /sbin/hotplug; pci_insert_device does not call
/sbin/hotplug.
diff -Nru a/drivers/pci/hotplug.c b/drivers/pci/hotplug.c
--- a/drivers/pci/hotplug.c Tue Nov 5 17:26:33 2002
+++ b/drivers/pci/hotplug.c Tue Nov 5 17:26:33 2002
@@ -71,8 +71,7 @@
* @bus: where to insert it
*
* Link the device to both the global PCI device chain and the
- * per-bus list of devices, add the /proc entry, and notify
- * userspace (/sbin/hotplug).
+ * per-bus list of devices, add the /proc entry.
*/
void
pci_insert_device(struct pci_dev *dev, struct pci_bus *bus)
diff -Nru a/drivers/pci/probe.c b/drivers/pci/probe.c
--- a/drivers/pci/probe.c Tue Nov 5 17:26:33 2002
+++ b/drivers/pci/probe.c Tue Nov 5 17:26:33 2002
@@ -480,8 +480,7 @@
/*
* Link the device to both the global PCI device chain and
- * the per-bus list of devices and call /sbin/hotplug if we
- * should.
+ * the per-bus list of devices and add the /proc entry.
*/
pci_insert_device (dev, bus);
next prev parent reply other threads:[~2002-11-06 1:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 1:36 [BK PATCH] PCI hotplug changes for 2.5.46 Greg KH
2002-11-06 1:37 ` Greg KH [this message]
2002-11-06 1:37 ` Greg KH
2002-11-06 1:38 ` [PATCH] " Greg KH
2002-11-06 1:39 ` Greg KH
2002-11-06 1:43 ` Greg KH
2002-11-06 1:43 ` Greg KH
2002-11-06 1:44 ` Greg KH
2002-11-06 1:45 ` Greg KH
2002-11-06 1:46 ` Greg KH
2002-11-06 1:47 ` 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=20021106013708.GR18627@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.