From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Linus Walleij <linusw@kernel.org>,
Drew Fustini <fustini@kernel.org>
Subject: Re: [PATCH 1/3] soc: tegra: Make ARCH_TEGRA_SOC_FOO defaults for Nvidia Tegra
Date: Tue, 17 Feb 2026 09:53:32 +0000 [thread overview]
Message-ID: <aZQ6nF9NJA9bqjSD@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260217-soc-tegra-arch-kconfig-v1-1-81bf5674d032@oss.qualcomm.com>
On Tue, Feb 17, 2026 at 10:16:36AM +0100, Krzysztof Kozlowski wrote:
> By convention, only one globally selectable ARCH_PLATFORM is expected
> for given SoC platform, defined in arch/arm64/Kconfig.platforms or
> arch/arm/mach-*/Kconfig, because we target a single multi-platform
> kernel image.
>
> Platforms wanting different granularity, e.g. due to size constraints on
> their devices, should be sure that globally only one ARCH_PLTAFORM is
typo: ARCH_PLATFORM
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-02-17 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 9:16 [PATCH 0/3] arm64: tegra: Make ARCH_TEGRA_SOC_FOO defaults for Nvidia Tegra Krzysztof Kozlowski
2026-02-17 9:16 ` [PATCH 1/3] soc: " Krzysztof Kozlowski
2026-02-17 9:53 ` Russell King (Oracle) [this message]
2026-02-17 9:16 ` [PATCH 2/3] ARM: tegra: defconfig: Drop redundant ARCH_TEGRA_foo_SOC Krzysztof Kozlowski
2026-02-17 9:16 ` [PATCH 3/3] arm64: " Krzysztof Kozlowski
2026-02-17 10:03 ` [PATCH 0/3] arm64: tegra: Make ARCH_TEGRA_SOC_FOO defaults for Nvidia Tegra Thierry Reding
2026-02-19 17:46 ` Linus Walleij
2026-02-19 17:46 ` Linus Walleij
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=aZQ6nF9NJA9bqjSD@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=fustini@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.