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 4/4] arm64: tegra: Device tree changes for v6.18-rc1
Date: Sun, 14 Sep 2025 08:39:25 +0200 [thread overview]
Message-ID: <20250914063927.89981-4-thierry.reding@gmail.com> (raw)
In-Reply-To: <20250914063927.89981-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 04f27a0fda6b6be104531eeb95d07ef1b3a72af8:
dt-bindings: arm: tegra: Add ASUS TF101G and SL101 (2025-09-11 18:28:57 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.18-arm64-dt
for you to fetch changes up to e1899da95f59240ed2d4a51d7a89c8b77c45ff06:
arm64: tegra: Add I2C nodes for Tegra264 (2025-09-11 18:35:23 +0200)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Device tree changes for v6.18-rc1
Add I2C nodes for Tegra264. These are currently unused but are needed
for subsequent audio patches, as well as various monitoring and other
auxiliary chips.
----------------------------------------------------------------
Kartik Rajput (1):
arm64: tegra: Add I2C nodes for Tegra264
Thierry Reding (1):
Merge branch 'for-6.18/dt-bindings' into for-6.18/arm64/dt
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 225 +++++++++++++++++++++++++++++++
1 file changed, 225 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 ` [GIT PULL 2/4] soc/tegra: " Thierry Reding
2025-09-14 6:39 ` [GIT PULL 3/4] ARM: tegra: Device tree changes " Thierry Reding
2025-09-14 6:39 ` Thierry Reding [this message]
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-4-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.