From: Aaron Tomlin <atomlin@redhat.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] module: Move module's Kconfig items in kernel/module/
Date: Wed, 13 Jul 2022 09:04:29 +0100 [thread overview]
Message-ID: <20220713080429.7r2xcpumnynhnyhe@ava.usersys.com> (raw)
In-Reply-To: <fdc6016e2414a26f17a17024d287087627052ea6.1657605146.git.christophe.leroy@csgroup.eu>
On Tue 2022-07-12 07:52 +0200, Christophe Leroy wrote:
> In init/Kconfig, the part dedicated to modules is quite large.
>
> Move it into a dedicated Kconfig in kernel/module/
>
> MODULES_TREE_LOOKUP was outside of the 'if MODULES', but as it is
> only used when MODULES are set, move it in with everything else to
> avoid confusion.
>
> MODULE_SIG_FORMAT is left in init/Kconfig because this configuration
> item is not used in kernel/modules/ but in kernel/ and can be
> selected independently from CONFIG_MODULES. It is for instance
> selected from security/integrity/ima/Kconfig.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> init/Kconfig | 293 +-----------------------------------------
> kernel/module/Kconfig | 293 ++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 294 insertions(+), 292 deletions(-)
> create mode 100644 kernel/module/Kconfig
Thanks Christophe!
Reviewed-by: Aaron Tomlin <atomlin@redhat.com>
--
Aaron Tomlin
prev parent reply other threads:[~2022-07-13 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 5:52 [PATCH v2] module: Move module's Kconfig items in kernel/module/ Christophe Leroy
2022-07-12 19:08 ` Luis Chamberlain
2022-07-13 8:04 ` Aaron Tomlin [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=20220713080429.7r2xcpumnynhnyhe@ava.usersys.com \
--to=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.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).