From: Krzysztof Kozlowski <krzk@kernel.org>
To: Albert Yang <yangzh0906@thundersoft.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Ge Gordon <gordon.ge@bst.ai>
Subject: Re: [PATCH v1 3/9] arm64: Kconfig: add ARCH_BST for bst silicons
Date: Wed, 28 May 2025 11:10:21 +0200 [thread overview]
Message-ID: <9f0d0109-3376-40f1-935a-bf341019956d@kernel.org> (raw)
In-Reply-To: <20250528085448.481215-1-yangzh0906@thundersoft.com>
On 28/05/2025 10:54, Albert Yang wrote:
> Add ARCH_BST for bst SoC series support.
> Add ARCH_BSTC1200 for BSTC1200 platform.
>
> Signed-off-by: Ge Gordon <gordon.ge@bst.ai>
> Signed-off-by: Albert Yang <yangzh0906@thundersoft.com>
> ---
> arch/arm64/Kconfig.platforms | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 8b76821f190f..b94c8c5d038c 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -402,4 +402,23 @@ config ARCH_ZYNQMP
> help
> This enables support for Xilinx ZynqMP Family
>
> +config ARCH_BSTC1200
B is not after Z. Anyway one ARCH entry per architecture, not per soc.
> + bool "BSTC1200 Platforms"
> + select SOC_NONCOHERENT
There is no such thing. You need to clean up all your patches from
downstream stuff. Please start working on upstream kernel.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-05-28 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 8:54 [PATCH v1 3/9] arm64: Kconfig: add ARCH_BST for bst silicons Albert Yang
2025-05-28 9:10 ` Krzysztof Kozlowski [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=9f0d0109-3376-40f1-935a-bf341019956d@kernel.org \
--to=krzk@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=gordon.ge@bst.ai \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=will@kernel.org \
--cc=yangzh0906@thundersoft.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