linux-kernel - Re: Applied "spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver" to the spi tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190212164940.GI20635@sirena.org.uk>
Date:   Tue, 12 Feb 2019 16:49:40 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Marek Vasut <marek.vasut@...il.com>
Cc:     Mason Yang <masonccyang@...c.com.tw>,
        Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
        linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
        bbrezillon@...nel.org, linux-renesas-soc@...r.kernel.org,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        juliensu@...c.com.tw, Simon Horman <horms@...ge.net.au>,
        zhengxunli@...c.com.tw
Subject: Re: Applied "spi: Add Renesas R-Car Gen3 RPC-IF SPI controller
 driver" to the spi tree

On Tue, Feb 12, 2019 at 02:43:59PM +0000, Mark Brown wrote:

> Mason had submitted a new verison a couple of weeks ago and there'd been
> no replies on the new version so I'd thought that all the prior issues
> had been addressed.  I guess that's not the case?  The thread on the
> version before was a bit long but seemed to peter out, though looking at
> the archives it seems the main issue was that Mason stopped replying.

Following some IRC discussion with Marek and Sergei I've dropped these
for now.  The interaction with the HyperFlash support seems unclear
still and might be a bit more than a simple refactoring, worst case
it'll be binding incompatible though hopefully not.  Mason, if you could
work with them to figure out the MFD that'll be needed the driver looks
fine from a SPI subsystem point of view.

Sorry about the confusion for everyone here.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)