From: Michal Marek <mmarek@suse.cz>
To: Kiran Raparthy <kumarsharma.r@gmail.com>, linux-kernel@vger.kernel.org
Cc: Rom Lemarchand <romlem@android.com>,
linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [RFC] kbuild: make it possible to specify the module output dir
Date: Wed, 18 Feb 2015 16:05:48 +0100 [thread overview]
Message-ID: <54E4AA4C.4050509@suse.cz> (raw)
In-Reply-To: <1423479528-27027-1-git-send-email-kumarsharma.r@gmail.com>
On 2015-02-09 11:58, Kiran Raparthy wrote:
> From: Rom Lemarchand <romlem@android.com>
>
> kbuild: make it possible to specify the module output dir
>
> Make modinst_dir user-defined on the command line.
>
> This allows to do things like:
> make MODLIB=output/ modinst_dir=. modules_install
>
> to ensure all the .ko are in the output/ directory.
Please explain the use case and why it is needed. There are two
user-changeable variables used by modules_install:
INSTALL_MOD_PATH - prepended to /lib/modules/..., to allow installation
to a staging directory by non-root
INSTALL_MOD_DIR - for out-of-tree modules; specifies the subdirectory
of /lib/modules/.../ to put the modules under
(default: "extra").
The hierarchy used in the source tree is reflected under
/lib/modules/.../extra, but that should not be an issue.
Michal
prev parent reply other threads:[~2015-02-18 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 10:58 [RFC] kbuild: make it possible to specify the module output dir Kiran Raparthy
2015-02-16 4:36 ` Kiran Kumar
2015-02-18 15:05 ` Michal Marek [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=54E4AA4C.4050509@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@android.com \
--cc=kumarsharma.r@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romlem@android.com \
/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