From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Fixes for v4.10
Date: Mon, 12 Dec 2016 09:30:00 +0100 [thread overview]
Message-ID: <cover.1481530910.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM based SoC fixes for v4.10.
This provides an sd0_uhs node rather than duplicate sdh0 nodes
resolving an error introduced in a clean-up patch.
This pull request is based on "Second Round of Renesas ARM Based SoC DT
Updates for v4.10", tagged as renesas-arm64-dt2-for-v4.10,
which you have already pulled. The error corrected by this change
was introduced in that pull-request.
The following changes since commit 5de68961cf5618c1ce5bb15848b36121247f23d5:
arm64: dts: r8a7796: Add device node for PRR (2016-11-21 10:18:53 +0100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-fixes-for-v4.10
for you to fetch changes up to 8ebcb400af619ee0ddeb39c06fc35511b20cc697:
arm64: dts: h3ulcb: Provide sd0_uhs node (2016-12-08 14:29:17 +0100)
----------------------------------------------------------------
Renesas ARM Based SoC Fixes for v4.10
* Provide sd0_uhs node
----------------------------------------------------------------
Simon Horman (1):
arm64: dts: h3ulcb: Provide sd0_uhs node
arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2016-12-12 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 8:30 Simon Horman [this message]
2016-12-12 8:30 ` [PATCH] arm64: dts: h3ulcb: Provide sd0_uhs node Simon Horman
2017-01-04 15:10 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.10 Arnd Bergmann
2017-01-05 7:56 ` Simon Horman
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=cover.1481530910.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).