From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Vignesh Raghavendra <vigneshr@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: multi_v7_defconfig: Add more TI Keystone support
Date: Wed, 24 Jan 2024 10:41:41 -0600 [thread overview]
Message-ID: <20240124164141.e6sdftiqxoxr6k7t@ravage> (raw)
In-Reply-To: <20240124162857.111915-1-afd@ti.com>
On 10:28-20240124, Andrew Davis wrote:
> The Keystone platforms used their own keystone_defconfig mostly to
> enable CONFIG_ARM_LPAE which could not be added to the multi_v7 config.
> Now that we have multi_v7_lpae_defconfig/lpae.config target we can and
> should use that defconfig for Keystone. Add the remaining must have
> options for Keystone support to multi_v7_defconfig.
>
Please state bloat-o-meter impact on vmlinux.
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> arch/arm/configs/multi_v7_defconfig | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-24 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 16:28 [PATCH 1/2] ARM: multi_v7_defconfig: Add more TI Keystone support Andrew Davis
2024-01-24 16:28 ` [PATCH 2/2] ARM: configs: keystone: Remove this defconfig Andrew Davis
2024-01-24 16:41 ` Nishanth Menon
2024-01-24 17:31 ` Andrew Davis
2024-01-24 18:04 ` Nishanth Menon
2024-01-24 18:52 ` Andrew Davis
2024-01-24 19:56 ` Arnd Bergmann
2024-01-25 13:41 ` Nishanth Menon
2024-01-24 16:41 ` Nishanth Menon [this message]
2024-01-24 16:59 ` [PATCH 1/2] ARM: multi_v7_defconfig: Add more TI Keystone support Andrew Davis
2024-01-24 17:21 ` Nishanth Menon
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=20240124164141.e6sdftiqxoxr6k7t@ravage \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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