From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Arnd Bergmann <arnd@arndb.de>,
soc@kernel.org, Sumit Gupta <sumitg@nvidia.com>,
Petlozu Pravareshwar <petlozup@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: tegra: fix CPU_BIG_ENDIAN dependencies
Date: Fri, 16 Dec 2022 14:20:09 +0100 [thread overview]
Message-ID: <Y5xwiV/OiAKmnsVt@orome> (raw)
In-Reply-To: <20221215165336.1781080-1-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Thu, Dec 15, 2022 at 05:53:21PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> My previous patch to prevent BPMP from being enabled on big
> endian kernels caused a build regression:
>
> WARNING: unmet direct dependencies detected for TEGRA_BPMP
> Depends on [n]: ARCH_TEGRA [=y] && TEGRA_HSP_MBOX [=y] && TEGRA_IVC [=y] && !CPU_BIG_ENDIAN [=y]
> Selected by [y]:
> - ARCH_TEGRA_186_SOC [=y] && ARCH_TEGRA [=y] && ARM64 [=y]
> - ARCH_TEGRA_194_SOC [=y] && ARCH_TEGRA [=y] && ARM64 [=y]
> - ARCH_TEGRA_234_SOC [=y] && ARCH_TEGRA [=y] && ARM64 [=y]
>
> Add even more such dependencies for the SoC types that use
> the BPMP driver.
>
> Fixes: 4ddb1bf1a837 ("tegra: mark BPMP driver as little-endian only")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/soc/tegra/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
Do you want to pick this up into ARM SoC directly? If so:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-16 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:53 [PATCH] soc: tegra: fix CPU_BIG_ENDIAN dependencies Arnd Bergmann
2022-12-16 13:20 ` Thierry Reding [this message]
2022-12-19 16:00 ` patchwork-bot+linux-soc
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=Y5xwiV/OiAKmnsVt@orome \
--to=thierry.reding@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=petlozup@nvidia.com \
--cc=soc@kernel.org \
--cc=sumitg@nvidia.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