From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Heidelberg <david@ixit.cz>
Cc: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: multi_v7_defconfig add /proc/config.gz
Date: Mon, 12 Jun 2023 23:35:06 +0200 [thread overview]
Message-ID: <2023061257-robotics-dinginess-c30c@gregkh> (raw)
In-Reply-To: <20230612210208.109267-1-david@ixit.cz>
On Mon, Jun 12, 2023 at 11:02:07PM +0200, David Heidelberg wrote:
> While 32-bit ARM isn't that widespread, multi_v7_defconfig is used for
> building more generic images, where having access to config can be handy.
>
> arm64 and x86_64 already bundle config.gz, so this is an effort to provide
> the same level of comfort with ARMv7 devices.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> arch/arm/configs/multi_v7_defconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index 084cc612ea23..f40b5936ccbf 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -1,6 +1,8 @@
> CONFIG_SYSVIPC=y
> CONFIG_NO_HZ_IDLE=y
> CONFIG_HIGH_RES_TIMERS=y
> +CONFIG_IKCONFIG=y
> +CONFIG_IKCONFIG_PROC=y
Why not make this a module?
thanks,
greg k-h
prev parent reply other threads:[~2023-06-12 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 21:02 [PATCH] ARM: multi_v7_defconfig add /proc/config.gz David Heidelberg
2023-06-12 21:35 ` Greg Kroah-Hartman [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=2023061257-robotics-dinginess-c30c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=david@ixit.cz \
--cc=fabrice.gasnier@foss.st.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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