linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Tejun Heo" <htejun@gmail.com>
Cc: "Jon Masters" <jonathan@jonmasters.org>,
	"Rusty Russell" <rusty@rustcorp.com.au>,
	"Sam Ravnborg" <sam@ravnborg.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>,
	notting@redhat.com, "Greg KH" <greg@kroah.com>
Subject: Re: [PATCH] depmod: sort output according to modules.order, take #2
Date: Sun, 16 Nov 2008 17:13:42 +0100	[thread overview]
Message-ID: <ac3eb2510811160813j5965a92cj1f4ad6979ecd7090@mail.gmail.com> (raw)
In-Reply-To: <491FAEB8.5010501@gmail.com>

On Sun, Nov 16, 2008 at 06:25, Tejun Heo <htejun@gmail.com> wrote:
> Jon Masters wrote:
>> On Thu, 2008-11-13 at 20:36 +0900, Tejun Heo wrote:
>>
>>> Jon, this patch hasn't made into module-init-tools
>>
>> I'm redoing it to cope with the binary sorted output files we have now -
>> i.e. we can't just rely upon the order of modules.dep any more, what
>> you're actually trying to do with modules.order is ensure that e.g.
>> modules providing conflicting aliases get handled in "order".
>
> Yes, that's right.  Ah... so, now modules.dep is sorted to speed up
> module look up?

It's a match tree, stored in a binary file format, not a specific ordering.

> Is this code already in module-init-tools?

http://git.kernel.org/?p=utils/kernel/module-init-tools/module-init-tools.git;a=summary

Kay

  reply	other threads:[~2008-11-16 16:13 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 [this message]
2007-12-13  7:12   ` Greg KH
2007-12-09  8:11 ` [PATCH] kbuild: implement " Sam Ravnborg
2007-12-13  7:11 ` Greg KH

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=ac3eb2510811160813j5965a92cj1f4ad6979ecd7090@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=greg@kroah.com \
    --cc=htejun@gmail.com \
    --cc=jonathan@jonmasters.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 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).