From: Arnd Bergmann <arnd@bergmann-dalldorf.de>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Module alias and device table support.
Date: Sat, 01 Feb 2003 11:36:34 +0100 [thread overview]
Message-ID: <200302011055.LAA29753@post.webmailer.de> (raw)
In-Reply-To: 20030201073007$3e7f@gated-at.bofh.it
Kai Germaschewski wrote:
> Alright. I think we're heading towards a generic postprocessor here, which
> takes the .o, extracts information as necessary and generates some .c file
> which contains e.g. checksums for the unresolved symbols (when MODVERSIONS
> is selected), a section to record which modules we depend on, an alias
> section etc. This .c is then compiled and linked into the final .ko
...
> Yup, I think modversions should have a little time to settle first.
> There's really only one tricky point with modversions (and the other stuff
> above), i.e. we need a complete list of all modules. With people
> playing tricks with "make SUBDIRS=..." that needs some care to not go
> accidentally wrong.
Worse that "make SUBDIRS=...", what do you think can be done about third
party modules? After all, I thought they are what modversions are about.
I don't see how you can reliably find the list of required modules when
you build a module outside of the kernel tree.
Arnd <><
next parent reply other threads:[~2003-02-01 10:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030201073007$5418@gated-at.bofh.it>
[not found] ` <20030201073007$3e7f@gated-at.bofh.it>
2003-02-01 10:36 ` Arnd Bergmann [this message]
2003-02-04 17:45 [PATCH] Module alias and device table support Adam J. Richter
2003-02-05 0:17 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 17:25 Adam J. Richter
2003-01-31 0:09 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-04 14:49 ` Roman Zippel
2003-02-03 13:40 ` Roman Zippel
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=200302011055.LAA29753@post.webmailer.de \
--to=arnd@bergmann-dalldorf.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.