From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Roadmap to restoring working usb module autoloading?
Date: Sun, 21 Jan 2001 03:17:02 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98004708406001@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97999756331097@msgid-missing>
>> = Adam Richter
> = Keith Owens
>"Adam J. Richter" <adam@yggdrasil.com> wrote:
>> Of course, it's also easy enough to stip out the code from
>>depmod that complains about the device ID version number differences
>>without changing anything else if device ID version numbers do get
>>integrated.
>And break everything downstream from depmod. Most (all?) of the
>utilities that read the depmod generated maps rely on the header line
>to tell them which format of table they are reading. [...]
Whoa! I did not say strip out the header lines. I said allow
device ID structure version numbers to be different. For example,
I might have version 2 usb_device_id's and version 1 parport_device_id's.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-21 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 13:32 Roadmap to restoring working usb module autoloading? Adam J. Richter
2001-01-20 20:55 ` David Brownell
2001-01-21 2:25 ` Adam J. Richter
2001-01-21 2:47 ` Keith Owens
2001-01-21 3:17 ` Adam J. Richter [this message]
2001-01-21 3:21 ` Keith Owens
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=marc-linux-hotplug-98004708406001@msgid-missing \
--to=adam@yggdrasil.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).