From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms@verge.net.au>
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT
Date: Thu, 26 Jan 2017 12:36:57 +0100 [thread overview]
Message-ID: <20170126113657.GA2281@katana> (raw)
In-Reply-To: <20170126102713.GA27721@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
> > Do you have the HS200 enablement patches in that branch? They are
> > currently in -next.
>
> I tried mmc/next (but didn't notice anything special there).
> Which patches should I be looking for?
The series starting with 59c21074b582aa ("mmc: sh_mobile_sdhi: simplify
accessing DT data") up to 8c81459fa8adec ("mmc: sh_mobile_sdhi: enable
HS200").
Do you already fetch from Ulf's kernel.org tree? He switched away from
the Linaro tree for MMC for a while. I only realized when he complained
that he can't apply my patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-26 11:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 17:39 [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT Wolfram Sang
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 [this message]
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=20170126113657.GA2281@katana \
--to=wsa@the-dreams.de \
--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 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.