From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver Core patches for 2.6.9
Date: Tue, 19 Oct 2004 09:36:26 -0700 [thread overview]
Message-ID: <10982037861198@kroah.com> (raw)
In-Reply-To: <1098203784644@kroah.com>
ChangeSet 1.1939.1.49, 2004/09/22 16:25:38-07:00, greg@kroah.com
[PATCH] PCI: add "struct module *" to struct pci_driver to show symlink in sysfs for pci drivers.
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
drivers/pci/pci-driver.c | 1 +
include/linux/pci.h | 2 ++
2 files changed, 3 insertions(+)
diff -Nru a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
--- a/drivers/pci/pci-driver.c 2004-10-19 09:22:19 -07:00
+++ b/drivers/pci/pci-driver.c 2004-10-19 09:22:19 -07:00
@@ -404,6 +404,7 @@
drv->driver.bus = &pci_bus_type;
drv->driver.probe = pci_device_probe;
drv->driver.remove = pci_device_remove;
+ drv->driver.owner = drv->owner;
drv->driver.kobj.ktype = &pci_driver_kobj_type;
pci_init_dynids(&drv->dynids);
diff -Nru a/include/linux/pci.h b/include/linux/pci.h
--- a/include/linux/pci.h 2004-10-19 09:22:19 -07:00
+++ b/include/linux/pci.h 2004-10-19 09:22:19 -07:00
@@ -631,9 +631,11 @@
unsigned int use_driver_data:1; /* pci_driver->driver_data is used */
};
+struct module;
struct pci_driver {
struct list_head node;
char *name;
+ struct module *owner;
const struct pci_device_id *id_table; /* must be non-NULL for probe to be called */
int (*probe) (struct pci_dev *dev, const struct pci_device_id *id); /* New device inserted */
void (*remove) (struct pci_dev *dev); /* Device removed (NULL if not a hot-plug capable driver) */
next prev parent reply other threads:[~2004-10-22 7:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 16:34 [BK PATCH] " Greg KH
2004-10-19 16:35 ` [PATCH] " Greg KH
2004-10-19 16:35 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH [this message]
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-23 20:20 ` Kronos
2004-10-23 20:34 ` Greg KH
2004-10-23 21:46 ` Kronos
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=10982037861198@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome