From: Michael Ellerman <mpe@ellerman•id.au>
To: Kees Cook <keescook@chromium•org>,
Masahiro Yamada <masahiroy@kernel•org>
Cc: linux-s390@vger•kernel.org, Randy Dunlap <rdunlap@infradead•org>,
Kees Cook <keescook@chromium•org>,
linux-kbuild@vger•kernel.org, x86@kernel•org,
linux-kernel@vger•kernel.org, linux-hardening@vger•kernel.org,
linux-riscv@lists•infradead.org, linuxppc-dev@lists•ozlabs.org,
linux-arm-kernel@lists•infradead.org,
Nicolas Schier <nicolas@fjasle•eu>
Subject: Re: [PATCH v3] kbuild: Show marked Kconfig fragments in "help"
Date: Sat, 02 Sep 2023 11:37:22 +1000 [thread overview]
Message-ID: <87fs3xicdp.fsf@mail.lhotse> (raw)
In-Reply-To: <20230831191335.give.534-kees@kernel.org>
Kees Cook <keescook@chromium•org> writes:
> Currently the Kconfig fragments in kernel/configs and arch/*/configs
> that aren't used internally aren't discoverable through "make help",
> which consists of hard-coded lists of config fragments. Instead, list
> all the fragment targets that have a "# Help: " comment prefix so the
> targets can be generated dynamically.
>
> Add logic to the Makefile to search for and display the fragment and
> comment. Add comments to fragments that are intended to be direct targets.
>
> Cc: Nicolas Schier <nicolas@fjasle•eu>
> Cc: Michael Ellerman <mpe@ellerman•id.au>
> Cc: Christophe Leroy <christophe.leroy@csgroup•eu>
> Cc: Randy Dunlap <rdunlap@infradead•org>
> Cc: linux-kernel@vger•kernel.org
> Cc: x86@kernel•org
> Cc: linux-arm-kernel@lists•infradead.org
> Cc: linuxppc-dev@lists•ozlabs.org
> Cc: linux-riscv@lists•infradead.org
> Cc: linux-s390@vger•kernel.org
> Cc: linux-kbuild@vger•kernel.org
> Cc: linux-hardening@vger•kernel.org
> Signed-off-by: Kees Cook <keescook@chromium•org>
> Co-developed-by: Masahiro Yamada <masahiroy@kernel•org>
> ---
> v3:
> - Use Makefile logic from Masahiro Yamada
> - Use "# Help: " prefix, but only on desired fragment targets
> v2: https://lore.kernel.org/all/20230825194329.gonna.911-kees@kernel.org
> v1: https://lore.kernel.org/all/20230824223606.never.762-kees@kernel.org
> ---
> Makefile | 1 -
> arch/arm/configs/dram_0x00000000.config | 1 +
> arch/arm/configs/dram_0xc0000000.config | 1 +
> arch/arm/configs/dram_0xd0000000.config | 1 +
> arch/arm/configs/lpae.config | 1 +
> arch/arm64/configs/virt.config | 1 +
> arch/powerpc/configs/disable-werror.config | 1 +
> arch/powerpc/configs/security.config | 4 +++-
Acked-by: Michael Ellerman <mpe@ellerman•id.au> (powerpc)
cheers
next prev parent reply other threads:[~2023-09-02 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 19:13 [PATCH v3] kbuild: Show marked Kconfig fragments in "help" Kees Cook
2023-09-01 7:58 ` Masahiro Yamada
2023-09-01 19:50 ` Kees Cook
2023-09-02 6:17 ` Masahiro Yamada
2023-09-02 1:37 ` Michael Ellerman [this message]
2023-09-02 18:17 ` Nicolas Schier
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=87fs3xicdp.fsf@mail.lhotse \
--to=mpe@ellerman$(echo .)id.au \
--cc=keescook@chromium$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-hardening@vger$(echo .)kernel.org \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=masahiroy@kernel$(echo .)org \
--cc=nicolas@fjasle$(echo .)eu \
--cc=rdunlap@infradead$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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