From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa@the-dreams.de>
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 11:01:17 +0100 [thread overview]
Message-ID: <20170126100116.GC21851@verge.net.au> (raw)
In-Reply-To: <20170113083928.GD1446@katana>
On Fri, Jan 13, 2017 at 09:39:28AM +0100, Wolfram Sang wrote:
> > Sorry for missing these.
> > I have queued them up for v4.11.
>
> Thank you!
On my r8a7796/salvator-x I see the following with this series applied:
sh_mobile_sdhi ee140000.sd: timeout waiting for hardware interrupt (CMD13)
I am currently thinking in terms of dropping this series from v4.11
so we can revisit it for v4.12.
next prev parent reply other threads:[~2017-01-26 10:01 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 [this message]
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=20170126100116.GC21851@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).