From: Thierry Reding <thierry.reding@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] soc/tegra: Fixes for v7.2
Date: Fri, 3 Jul 2026 16:40:36 +0200 [thread overview]
Message-ID: <20260703144042.1190046-2-thierry.reding@kernel.org> (raw)
In-Reply-To: <20260703144042.1190046-1-thierry.reding@kernel.org>
From: Thierry Reding <thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 8b8ee2e56f951ccf41d98eebe73195cea487cd48:
soc/tegra: Use ARM SMCCC to get chip ID, revision, and platform info (2026-05-29 14:42:09 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.2-soc-fixes
for you to fetch changes up to 265d5d4032c5f6eb089a6e6241d37fdbde7da180:
soc/tegra: fuse: Fix spurious straps warning on SMCCC platforms (2026-06-22 09:25:36 +0200)
Thanks,
Thierry
----------------------------------------------------------------
soc/tegra: Fixes for v7.2
Fix a spurious WARN() that was checking for an outdated condition.
----------------------------------------------------------------
Breno Leitao (1):
soc/tegra: fuse: Fix spurious straps warning on SMCCC platforms
drivers/soc/tegra/fuse/tegra-apbmisc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next prev parent reply other threads:[~2026-07-03 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 14:40 [GIT PULL 1/3] soc/tegra: pmc: Fixes for v7.2 Thierry Reding
2026-07-03 14:40 ` Thierry Reding [this message]
2026-07-03 14:40 ` [GIT PULL 3/3] arm64: tegra: Device tree fixes " Thierry Reding
2026-07-10 13:00 ` [GIT PULL 1/3] soc/tegra: pmc: Fixes " 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=20260703144042.1190046-2-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@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.