From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: rusty@rustcorp.com.au, kaos <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.47bk2 + current modutils == broken hotplug
Date: Wed, 13 Nov 2002 12:40:51 -0800 [thread overview]
Message-ID: <3DD2B8D3.6060106@pacbell.net> (raw)
In-Reply-To: 20021113201710.GB7238@kroah.com
Greg KH wrote:
> On Wed, Nov 13, 2002 at 12:11:01PM -0800, David Brownell wrote:
>
>>The module-init-tools-0.6.tar.gz utilities (or something
>>related -- kbuild changes?) break hotplug since they no
>>longer produce the /lib/modules/$(uname -r)/modules.*map
>>files as output ... so the hotplug agents don't have the
>>pre-built database mapping device info to drivers.
>
>
> Last I heard, Rusty's still working on this. He's also going to be
> changing the format so we don't expose kernel structures to userspace,
> which would be a good thing.
So long as the _information_ in those structures stays available, good.
And it'd be handy if the text format for that information didn't change;
how it's stored in object modules doesn't matter.
> In short, he knows this is a requirement, and shouldn't be broken for
> long.
Good, that's important.
- Dave
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2002-11-13 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 20:11 2.5.47bk2 + current modutils == broken hotplug David Brownell
2002-11-13 20:17 ` Greg KH
2002-11-13 20:40 ` David Brownell [this message]
2002-11-13 20:59 ` Jeff Garzik
2002-11-13 21:07 ` Greg KH
2002-11-13 22:45 ` David Brownell
2002-11-13 21:24 ` Jeff Garzik
2002-11-13 23:00 ` David Brownell
2002-11-14 3:46 ` Rusty Russell
2002-11-14 8:02 ` David Brownell
2002-11-14 10:01 ` Rusty Russell
2002-11-14 16:19 ` David Brownell
2002-11-14 17:42 ` Rusty Russell
2002-11-14 10:41 ` Gerd Knorr
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=3DD2B8D3.6060106@pacbell.net \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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