From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Simon Horman <horms@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT
Date: Wed, 4 Jan 2017 18:39:52 +0100 [thread overview]
Message-ID: <20170104173954.3135-1-wsa+renesas@sang-engineering.com> (raw)
Simon,
as Ulf picked up the driver patches for HS200 support, it is now safe to pick
up the DTS patches, I'd say? I rebased them to the dt-for-4.11 branch.
All the best,
Wolfram
Wolfram Sang (2):
arm64: dts: r8a7795: enable HS200 for eMMC
arm64: dts: r8a7796: enable HS200 for eMMC
arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 1 +
arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts | 1 +
2 files changed, 2 insertions(+)
--
2.10.2
next reply other threads:[~2017-01-04 17:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 17:39 Wolfram Sang [this message]
2017-01-04 17:39 ` [PATCH RESEND 1/2] arm64: dts: r8a7795: enable HS200 for eMMC Wolfram Sang
2017-01-04 17:39 ` [PATCH RESEND 2/2] arm64: dts: r8a7796: " Wolfram Sang
2017-01-12 22:43 ` [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT Wolfram Sang
2017-01-13 8:37 ` Simon Horman
2017-01-13 8:39 ` Wolfram Sang
2017-01-26 10:01 ` Simon Horman
2017-01-26 10:03 ` Wolfram Sang
2017-01-26 10:27 ` Simon Horman
2017-01-26 11:36 ` Wolfram Sang
2017-01-26 13:33 ` Simon Horman
2017-01-26 13:54 ` Wolfram Sang
2017-01-26 14:06 ` Simon Horman
2017-01-26 14:16 ` Wolfram Sang
2017-01-26 14:40 ` Geert Uytterhoeven
2017-01-26 14:51 ` Wolfram Sang
2017-01-26 15:24 ` Simon Horman
2017-01-26 20:17 ` Wolfram Sang
2017-01-27 6:33 ` Simon Horman
2017-01-27 7:27 ` Wolfram Sang
2017-01-27 8:16 ` Simon Horman
2017-04-08 11:06 ` Wolfram Sang
2017-04-08 11:20 ` Wolfram Sang
2017-01-26 13:58 ` Geert Uytterhoeven
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=20170104173954.3135-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@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;
as well as URLs for NNTP newsgroup(s).