linux-kernel - Re: [PATCH v4 0/3] mtd: rawnand: ams-delta: Cleanups and optimizations

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed, 19 Sep 2018 10:46:39 +0200
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Tony Lindgren <tony@...mide.com>
Cc:     Janusz Krzysztofik <jmkrzyszt@...il.com>,
        Boris Brezillon <boris.brezillon@...tlin.com>,
        Richard Weinberger <richard@....at>,
        David Woodhouse <dwmw2@...radead.org>,
        Brian Norris <computersforpeace@...il.com>,
        Marek Vasut <marek.vasut@...il.com>,
        linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/3] mtd: rawnand: ams-delta: Cleanups and
 optimizations

Hi Janusz,

Tony Lindgren <tony@...mide.com> wrote on Fri, 7 Sep 2018 09:45:24
-0700:

> Hi,
> 
> * Janusz Krzysztofik <jmkrzyszt@...il.com> [180905 20:56]:
> > On Wednesday, September 5, 2018 8:47:57 AM CEST Miquel Raynal wrote:  
> > > Patch 2/3 does not apply on nand/next. Indeed the driver does not look
> > > the same as in the diff.  
> > 
> > That's because I built it on top of my former series from the mid of July, 
> > containing "[PATCH v2 2/3 v4] mtd: rawnand: ams-delta: use GPIO lookup table". 
> > It was acked by you, Miquel, and supposed to be merged via linux-omap tree.  
> 
> Hmm I thought the plan was for dependencies to clear and then
> merge the rest via various driver trees.. Or at least I don't have
> the patch above tagged anywhere for me to merge. Then again, I
> try to forget everything posted before -rc1 just to stay sane :)
> 
> > > I don't see any changes on my side that could
> > > explain this so perhaps you could rebase on top of 4.19-rc2 (or
> > > nand/next, as you wish) and resend the series?  
> > 
> > As far as I can see, Tony hasn't applied that series yet, so maybe I can still 
> > move that patch out of there and insert it into this series in front of the 
> > other 3 patches and resend. That would however make patch 3/3 of that old 
> > series depend on this one.
> > 
> > Tony, what do you think?  
> 
> Yes please resend based on v4.19-rc1 or MTD next. If there
> are still pending dependencies, please let us know and we can
> set up an immutable branch against v4.19-rc1 with those for
> MTD and me to merge in as needed.
> 
> Regards,
> 
> Tony

AFAIR I didn't received any new patches from you since Tony suggestion.
If you haven't done it already, please rebase against nand/next before
sending patches (internal API changed a bit, it might be worth fixing
the conflicts before sending them).


Thanks,
Miquèl