From: Greg KH <greg@kroah.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Horst von Brand <brand@jupiter.cs.uni-dortmund.de>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [PATCH] Restore module support.
Date: Thu, 6 Feb 2003 20:06:06 -0800 [thread overview]
Message-ID: <20030207040606.GA30337@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302070037230.32518-100000@serv>
On Fri, Feb 07, 2003 at 01:01:01AM +0100, Roman Zippel wrote:
> Hi,
>
> On Thu, 6 Feb 2003, Greg KH wrote:
>
> > But what are the modutils numbers? :)
>
> There should be no real difference as I'd like to integrate Kai's patch too.
Ok, I'm confused, you're advocating putting back the old modutils
interface, but somehow not using the old modutils code? I don't
understand.
> > Come on, what Rusty did was the "right thing to do" and has made life
> > easier for all of the arch maintainers (or so says the ones that I've
> > talked to), and has made my life easier with regards to
> > MODULE_DEVICE_TABLE() logic, which will enable the /sbin/hotplug
> > scripts/binary to shrink a _lot_.
>
> What was the "right thing to do"?
> There were certainly a few interesting changes, but I'd like discuss them
> first. For example there is more than one solution to improve the
> MODULE_DEVICE_TABLE() logic (*), so how is Rusty's better?
Neither one of those proposals, no any others, were backed with working
examples. Rusty had the only working example of getting rid of the
userspace knowledge of the kernel data structures that I know of so far.
thanks,
greg k-h
next prev parent reply other threads:[~2003-02-07 4:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 0:09 [PATCH] Module alias and device table support Rusty Russell
2003-01-31 6:23 ` Kai Germaschewski
2003-01-31 9:41 ` Horst von Brand
2003-01-31 15:42 ` Ingo Oeser
2003-01-31 22:33 ` Roman Zippel
2003-02-01 0:48 ` Kai Germaschewski
2003-02-01 1:22 ` Roman Zippel
2003-02-01 2:59 ` Kai Germaschewski
2003-02-01 10:31 ` Roman Zippel
2003-02-01 3:49 ` Rusty Russell
2003-02-01 7:20 ` Kai Germaschewski
2003-02-01 23:02 ` Horst von Brand
2003-02-03 0:52 ` Rusty Russell
2003-02-03 2:49 ` John Levon
2003-02-03 10:34 ` Rusty Russell
2003-02-04 9:56 ` Horst von Brand
2003-02-05 0:00 ` Rusty Russell
2003-02-03 8:31 ` Horst von Brand
2003-02-03 10:52 ` Rusty Russell
2003-02-04 8:05 ` Horst von Brand
2003-02-04 8:51 ` Rusty Russell
2003-02-06 23:09 ` [PATCH] Restore module support Roman Zippel
2003-02-06 23:25 ` Greg KH
2003-02-07 0:01 ` Roman Zippel
2003-02-07 4:06 ` Greg KH [this message]
2003-02-07 9:39 ` Roman Zippel
2003-02-07 18:01 ` Roman Zippel
2003-02-07 0:10 ` Russell King
2003-02-07 4:53 ` Rusty Russell
2003-02-07 10:03 ` Russell King
2003-02-07 6:12 ` Kai Germaschewski
2003-02-07 9:46 ` Roman Zippel
2003-02-04 14:49 ` [PATCH] Module alias and device table support Roman Zippel
2003-02-03 13:40 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 23:49 [PATCH] Restore module support Adam J. Richter
2003-02-07 8:26 Rusty Russell
2003-02-07 10:05 ` Russell King
2003-02-08 4:32 ` Rusty Russell
2003-02-07 18:43 Luck, Tony
2003-02-07 19:50 ` Russell King
2003-02-07 21:15 Luck, Tony
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=20030207040606.GA30337@kroah.com \
--to=greg@kroah.com \
--cc=brand@jupiter.cs.uni-dortmund.de \
--cc=jgarzik@pobox.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=zippel@linux-m68k.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