From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: s.hauer@pengutronix.de, catalin.marinas@arm.com, will@kernel.org,
arnd@arndb.de, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] arm64: defconfig: select ARCH_NXP
Date: Mon, 12 Sep 2022 18:17:59 +0800 [thread overview]
Message-ID: <20220912101759.GB1728671@dragon> (raw)
In-Reply-To: <20220908003914.2062126-1-peng.fan@oss.nxp.com>
On Thu, Sep 08, 2022 at 08:39:14AM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> commit 566e373fe047 ("arm64: Kconfig.platforms: Group NXP platforms
> together") groups NXP platforms with ARCH_NXP, which cause the default
> build not support i.MX with arm64 defconfig, so default enable ARCH_NXP
> to resolve the issue.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Thanks for the patch, Peng! But I have queued a patch [1] from Michael.
Shawn
[1] https://lore.kernel.org/linux-arm-kernel/20220907070626.2933998-1-michael@walle.cc/T/
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 91e58cf59c99..07b9185f5937 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -47,6 +47,7 @@ CONFIG_ARCH_KEEMBAY=y
> CONFIG_ARCH_MEDIATEK=y
> CONFIG_ARCH_MESON=y
> CONFIG_ARCH_MVEBU=y
> +CONFIG_ARCH_NXP=y
> CONFIG_ARCH_MXC=y
> CONFIG_ARCH_NPCM=y
> CONFIG_ARCH_QCOM=y
> --
> 2.37.1
>
prev parent reply other threads:[~2022-09-12 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 0:39 [PATCH] arm64: defconfig: select ARCH_NXP Peng Fan (OSS)
2022-09-12 10:17 ` Shawn Guo [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=20220912101759.GB1728671@dragon \
--to=shawnguo@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=will@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