From: Greg KH <greg@kroah.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
notting@redhat.com, rusty@rustcorp.com.au, kay.sievers@vrfy.org
Subject: Re: [PATCH] kbuild: implement modules.order, take #2
Date: Wed, 12 Dec 2007 23:11:56 -0800 [thread overview]
Message-ID: <20071213071156.GC13764@kroah.com> (raw)
In-Reply-To: <475936CE.70703@gmail.com>
On Fri, Dec 07, 2007 at 09:04:30PM +0900, Tejun Heo wrote:
> When multiple built-in modules (especially drivers) provide the same
> capability, they're prioritized by link order specified by the order
> listed in Makefile. This implicit ordering is lost for loadable
> modules.
>
> When driver modules are loaded by udev, what comes first in
> modules.alias file is selected. However, the order in this file is
> indeterministic (depends on filesystem listing order of installed
> modules). This causes confusion.
>
> The solution is two-parted. This patch updates kbuild such that it
> generates and installs modules.order which contains the name of
> modules ordered according to Makefile. The second part is update to
> depmod such that it generates output files according to this file.
>
> Note that both obj-y and obj-m subdirs can contain modules and
> ordering information between those two are lost from beginning.
> Currently obj-y subdirs are put before obj-m subdirs.
>
> Sam Ravnborg cleaned up Makefile modifications and suggested using awk
> to remove duplicate lines from modules.order instead of using separate
> C program.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Bill Nottingham <notting@redhat.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
thanks for doing this, looks very nice.
greg k-h
prev parent reply other threads:[~2007-12-13 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 12:04 [PATCH] kbuild: implement modules.order, take #2 Tejun Heo
2007-12-07 12:07 ` [PATCH] depmod: sort output according to " Tejun Heo
2007-12-09 9:30 ` Tejun Heo
2008-01-02 11:13 ` Tejun Heo
2008-01-02 23:12 ` Rusty Russell
2008-01-02 23:58 ` Jon Masters
2008-11-13 11:36 ` Tejun Heo
2008-11-13 19:30 ` Jon Masters
2008-11-15 19:20 ` Jon Masters
2008-11-16 5:25 ` Tejun Heo
2008-11-16 16:13 ` Kay Sievers
2007-12-13 7:12 ` Greg KH
2007-12-09 8:11 ` [PATCH] kbuild: implement " Sam Ravnborg
2007-12-13 7:11 ` Greg KH [this message]
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=20071213071156.GC13764@kroah.com \
--to=greg@kroah.com \
--cc=htejun@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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 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.