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] arm64: tegra: Device tree fixes for v6.8
Date: Mon, 26 Feb 2024 15:45:35 +0100 [thread overview]
Message-ID: <20240226144536.1525704-1-thierry.reding@gmail.com> (raw)
Hi ARM SoC maintainers,
The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:
Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.8-arm64-dt
for you to fetch changes up to ff6bd76f4d997642ef390bffe42e93d6f7be87d3:
arm64: tegra: Fix Tegra234 MGBE power-domains (2024-02-22 17:58:59 +0100)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Device tree fixes for v6.8
This contains two fixes to make the MGBE Ethernet devices found on
Tegra234 work properly.
----------------------------------------------------------------
Jon Hunter (1):
arm64: tegra: Fix Tegra234 MGBE power-domains
Thierry Reding (1):
arm64: tegra: Set the correct PHY mode for MGBE
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts | 2 +-
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2024-02-26 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 14:45 Thierry Reding [this message]
2024-02-27 13:19 ` [GIT PULL] arm64: tegra: Device tree fixes for v6.8 Thierry Reding
2024-03-04 16:11 ` patchwork-bot+linux-soc
2024-03-04 16:12 ` patchwork-bot+linux-soc
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 17:48 Thierry Reding
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=20240226144536.1525704-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).