From: Jonas Zeiger <jonas.zeiger@talpidae.net>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] Makefile: allow modules_install if CONFIG_MODULES=n
Date: Wed, 03 Jun 2020 15:28:28 +0200 [thread overview]
Message-ID: <de8bd991ea596e9309a89e8cf58fd471@talpidae.net> (raw)
In-Reply-To: <CAK7LNARx2dcjedkN8cBq0veh6H1cVG6yyGq=Vf6xr2Bd_aHuRA@mail.gmail.com>
On 2020-05-31 20:16, Masahiro Yamada wrote:
> On Thu, May 28, 2020 at 1:44 PM Jonas Zeiger
> <jonas.zeiger@talpidae.net> wrote:
>>
>> Many applications check for available kernel features via:
>>
>> * /proc/modules (loaded modules, present if CONFIG_MODULES=y)
>> * $(MODLIB)/modules.builtin (builtin modules)
>>
>> They fail to detect features if the kernel was built with
>> CONFIG_MODULES=n
>> and modules.builtin isn't installed.
>>
>> Therefore, allow the Makefile's modules_install target to be used
>> always.
>>
>> Tested Makefile targets with different CONFIG_MODULES states:
>>
>> * (CONFIG_MODULES=n) modules_install: install modules.builtin etc.
>> * (CONFIG_MODULES=y) modules_install: produce same result as before
>> * (CONFIG_MODULES=y) modules_install: still fail if no modules.order
>> * (CONFIG_MODULES=y) modules: build modules, as before
>> * (CONFIG_MODULES=n) modules: still fail and warn
>>
>> Signed-off-by: Jonas Zeiger <jonas.zeiger@talpidae.net>
>
>
> Maybe, module.builtin and module.builtin.modinfo should be
> installed by 'make install' because they are byproducts of vmlinux.
Yes, thank you for this suggestion.
I will submit a new patch.
next prev parent reply other threads:[~2020-06-03 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 4:39 [PATCH] Makefile: allow modules_install if CONFIG_MODULES=n Jonas Zeiger
2020-05-31 18:16 ` Masahiro Yamada
2020-06-03 13:28 ` Jonas Zeiger [this message]
2020-06-03 13:34 ` [PATCH v2] Makefile: install modules.builtin even " Jonas Zeiger
2020-06-04 0:33 ` Masahiro Yamada
2020-06-09 16:38 ` Doug Anderson
2020-06-09 17:31 ` Guenter Roeck
2020-06-12 6:56 ` Masahiro Yamada
2020-06-12 13:31 ` Guenter Roeck
2020-06-12 15:35 ` Jonas Zeiger
2020-06-13 2:58 ` Masahiro Yamada
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=de8bd991ea596e9309a89e8cf58fd471@talpidae.net \
--to=jonas.zeiger@talpidae.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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