From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL 3/3] arm64: tegra: Device tree updates for v4.20-rc2
Date: Wed, 7 Nov 2018 15:53:50 +0100 [thread overview]
Message-ID: <20181107145350.29127-4-thierry.reding@gmail.com> (raw)
In-Reply-To: <20181107145350.29127-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit d9fd22447ba59a9b53a202fade977e82bfba8d8d:
arm64: tegra: I2C on Tegra194 is not compatible with Tegra114 (2018-09-26 15:50:59 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.20-rc2-arm64-dt
for you to fetch changes up to 47787b6b7d6981d979bdb01475cd3dd7626dbda3:
arm64: dts: tegra210: Add power-domains for xHCI (2018-10-25 14:31:25 +0200)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Device tree updates for v4.20-rc2
This contains a single change to populate power domains for the XUSB
device on Tegra210.
----------------------------------------------------------------
Jon Hunter (1):
arm64: dts: tegra210: Add power-domains for xHCI
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 2 ++
1 file changed, 2 insertions(+)
next prev parent reply other threads:[~2018-11-07 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 14:53 [GIT PULL 0/3] arm64: tegra: Updates for v4.20-rc2 Thierry Reding
2018-11-07 14:53 ` [GIT PULL 1/3] dt-bindings: " Thierry Reding
2018-11-07 14:53 ` [GIT PULL 2/3] soc/tegra: " Thierry Reding
2018-11-07 14:53 ` Thierry Reding [this message]
2018-11-07 16:31 ` [GIT PULL 0/3] arm64: tegra: " Olof Johansson
2018-11-08 12:16 ` Thierry Reding
2018-11-13 19:29 ` Olof Johansson
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=20181107145350.29127-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 \
/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