From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] soc/tegra: Changes for v6.18-rc1
Date: Sun, 14 Sep 2025 08:39:23 +0200 [thread overview]
Message-ID: <20250914063927.89981-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20250914063927.89981-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.18-soc
for you to fetch changes up to b9c01adedf38c69abb725a60a05305ef70dbce03:
soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (2025-09-11 18:19:02 +0200)
Thanks,
Thierry
----------------------------------------------------------------
soc/tegra: Changes for v6.18-rc1
NVMEM cells are added for Tegra114. These contain calibration data for
sensors and USB.
----------------------------------------------------------------
Svyatoslav Ryhel (1):
soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups
drivers/soc/tegra/fuse/fuse-tegra30.c | 122 ++++++++++++++++++++++++++++++++++
1 file changed, 122 insertions(+)
next prev parent reply other threads:[~2025-09-14 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 6:39 [GIT PULL 1/4] dt-bindings: Changes for v6.18-rc1 Thierry Reding
2025-09-14 6:39 ` Thierry Reding [this message]
2025-09-14 6:39 ` [GIT PULL 3/4] ARM: tegra: Device tree changes " Thierry Reding
2025-09-14 6:39 ` [GIT PULL 4/4] arm64: " Thierry Reding
2025-09-15 13:50 ` [GIT PULL 1/4] dt-bindings: Changes " patchwork-bot+linux-soc
2025-09-15 14:30 ` 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=20250914063927.89981-2-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--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.