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 4/6] firmware: tegra: Changes for v7.2-rc1
Date: Sun, 31 May 2026 08:08:21 +0200 [thread overview]
Message-ID: <20260531060825.1855391-4-thierry.reding@kernel.org> (raw)
In-Reply-To: <20260531060825.1855391-1-thierry.reding@kernel.org>
From: Thierry Reding <thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.2-firmware
for you to fetch changes up to 040eeafee0146b9d046caef501f387e107a59960:
firmware: tegra: bpmp: Add support for multi-socket platforms (2026-05-31 07:25:25 +0200)
Thanks,
Thierry
----------------------------------------------------------------
firmware: tegra: Changes for v7.2-rc1
This set of changes contains another attempt at resolving a Kconfig
dependency, propagates debugfs error codes and adds support for multiple
sockets to the BPMP driver.
----------------------------------------------------------------
Jon Hunter (2):
firmware: tegra: bpmp: Propagate debugfs errors
firmware: tegra: bpmp: Add support for multi-socket platforms
Sasha Levin (1):
firmware: tegra: Make TEGRA_IVC a hidden Kconfig symbol
drivers/firmware/tegra/Kconfig | 2 +-
drivers/firmware/tegra/bpmp-debugfs.c | 55 ++++++++++++++++++++++++++++-------
2 files changed, 46 insertions(+), 11 deletions(-)
next prev parent reply other threads:[~2026-05-31 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 6:08 [GIT PULL 1/6] dt-bindings: Changes for v7.2-rc1 Thierry Reding
2026-05-31 6:08 ` [GIT PULL 2/6] soc/tegra: " Thierry Reding
2026-05-31 6:08 ` [GIT PULL 3/6] soc/tegra: pmc: " Thierry Reding
2026-05-31 6:08 ` Thierry Reding [this message]
2026-06-09 14:38 ` [GIT PULL 4/6] firmware: tegra: " Arnd Bergmann
2026-05-31 6:08 ` [GIT PULL 5/6] ARM: tegra: Device tree changes " Thierry Reding
2026-05-31 6:08 ` [GIT PULL 6/6] arm64: tegra: Changes " Thierry Reding
2026-06-03 12:30 ` [GIT PULL 1/6] dt-bindings: " patchwork-bot+linux-soc
2026-06-09 16:40 ` 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=20260531060825.1855391-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox