From: Rusty Russell <rusty@rustcorp.com.au>
To: Jon Masters <jcm@jonmasters.org>
Cc: 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 20:13:45 +0930 [thread overview]
Message-ID: <201008162013.46252.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1281945814-9720-1-git-send-email-jcm@jonmasters.org>
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...
> ---
> Makefile | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index f3bdff8..2b904f2 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1325,7 +1325,9 @@ _emodinst_:
>
> PHONY += _emodinst_post
> _emodinst_post: _emodinst_
> +ifeq ($(INSTALL_MOD_PATH),)
> $(call cmd,depmod)
> +endif
>
> clean-dirs := $(addprefix _clean_,$(KBUILD_EXTMOD))
Thanks,
Rusty.
next prev parent reply other threads:[~2010-08-16 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 8:03 [PATCH] modules: don't call depmod when overriding external module install path Jon Masters
2010-08-16 10:43 ` Rusty Russell [this message]
2010-08-16 22:26 ` Jon Masters
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=201008162013.46252.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--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 \
/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