Re: [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Simon,

On Fri, Jan 27, 2017 at 09:16:08AM +0100, Simon Horman wrote:
> On Fri, Jan 27, 2017 at 08:27:28AM +0100, Wolfram Sang wrote:
> > 
> > > Using renesas-next without mmc-next I see the problem above on the M3-W.
> > > Using renesas-next with mmc-next I do not see the problem above.
> > > Using v4.10-rc2 I also do not see the problem above.
> > 
> > OK. So there is no problem with the code, at least.
> > 
> > > So I believe we should delay the integration change, which is currently in
> > > renesas-next, until the driver change in mmc-next hits Linus's tree.
> > 
> > Whatever you do, H3 and M3-W should be treated equally IMO.
> 
> Sure, that is reasonable. This is what I plan to do:
> 
> 1. Drop this series from v4.11
> 2. Re-queue them for v4.12 once the driver changes hit an rc release
>    - Please ping me one that happens

Ping :) Do I need to resend? If so, what branch should I base this on?

Have a nice weekend,

   Wolfram

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Samsung SOC]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux