From: Jon Masters <jonathan@jonmasters.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Jon Masters <jcm@jonmasters.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] modules: don't call depmod when overriding external module install path
Date: Mon, 16 Aug 2010 18:26:33 -0400 [thread overview]
Message-ID: <1281997594.27736.232.camel@constitution.bos.jonmasters.org> (raw)
In-Reply-To: <201008162013.46252.rusty@rustcorp.com.au>
On Mon, 2010-08-16 at 20:13 +0930, Rusty Russell wrote:
> On Mon, 16 Aug 2010 05:33:34 pm Jon Masters wrote:
> > Recent kernels include an additional call to depmod during the installation
> > of external kernel modules as a convenience, in order to ensure that those
> > modules are picked up by the module loading tools/initramfs scripts, etc.
> > Although this call is potentially of some value, it should not be made
> > when explicitly setting INSTALL_MOD_PATH to a different location. This
> > avoids creating extraneous modules.* files that will never be used.
> >
> > Signed-off-by: Jon Masters <jcm@jonmasters.org>
>
> Acked-by: Rusty Russell <rusty@rustcorp.com.au>
>
> I leave the Makefile stuff to the kbuild people...
Hey, thanks for forwarding. I figured I would do that, but I see you
already did. And yea, next time I'll ping the Kbuild folks directly.
Jon.
next prev parent reply other threads:[~2010-08-16 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1281945814-9720-1-git-send-email-jcm@jonmasters.org>
2010-08-16 10:43 ` [PATCH] modules: don't call depmod when overriding external module install path Rusty Russell
2010-08-16 22:26 ` Jon Masters [this message]
2010-08-17 2:51 ` Américo Wang
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=1281997594.27736.232.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=akpm@linux-foundation.org \
--cc=jcm@jonmasters.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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