From: Pavel Machek <pavel@suse.cz>
To: Patrick Mochel <mochel@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Kill unused pieces of linux/device.h
Date: Tue, 12 Feb 2002 10:01:28 +0100 [thread overview]
Message-ID: <20020212090128.GA627@elf.ucw.cz> (raw)
Hi!
This kills dead code, please apply,
Pavel
--- linux/include/linux/device.h Mon Feb 11 21:10:52 2002
+++ linux-dm/include/linux/device.h Mon Feb 11 21:57:56 2002
@@ -54,7 +54,6 @@
};
struct device;
-struct iobus;
struct device_driver {
int (*probe) (struct device * dev);
@@ -94,23 +93,6 @@
unsigned char *saved_state; /* saved device state */
};
-/*
- * struct bus_type - descriptor for a type of bus
- * There are some instances when you need to know what type of bus a
- * device is on. Instead of having some sort of enumerated integer type,
- * each struct iobus will have a pointer to a struct bus_type that gives
- * actually meaningful data.
- * There should be one struct bus_type for each type of bus (one for PCI,
- * one for USB, etc).
- */
-struct iobus_driver {
- char name[16]; /* ascii descriptor of type of bus */
- struct list_head node; /* node in global list of bus drivers */
-
- int (*scan) (struct iobus*);
- int (*add_device) (struct iobus*, char*);
-};
-
static inline struct device *
list_to_dev(struct list_head *node)
{
@@ -122,8 +104,6 @@
*/
extern int device_register(struct device * dev);
-extern int iobus_register(struct iobus * iobus);
-
extern int device_create_file(struct device *device, struct driver_file_entry * entry);
extern void device_remove_file(struct device * dev, const char * name);
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
reply other threads:[~2002-02-12 9:09 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=20020212090128.GA627@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@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
all inboxes | Powered by JetHome®