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  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:   Sun, 08 Oct 2017 11:53:11 +0200
From:   Robert Jarzmik <>
To:     Boris Brezillon <>
Cc:     Andrea Adami <>,,
        Wolfram Sang <>,
        Dmitry Eremin-Solenikov <>,
        Richard Weinberger <>,,
        Russell King <>,
        Haojian Zhuang <>,, Marek Vasut <>,,
        Cyrille Pitchen <>,
        Lee Jones <>,
        Brian Norris <>,
        David Woodhouse <>,
        Linus Walleij <>,
        Daniel Mack <>
Subject: Re: [PATCH v5 0/9] mtd: sharpslpart partition parser

Robert Jarzmik <> writes:

> Boris Brezillon <> writes:
>> Hi Robert,
>> Wait a bit before applying. I think patches 6 to 9 have a dependency on
>> patch 1 (it's not a build dependency, but NAND partitioning might be
>> wrong if you apply them), so we need to sync. What release is
>> pxa/for-next targeting? If it's 4.15 I can apply patch 1 just after
>> 4.14-rc1 is out and provide an immutable branch for you to pull in
>> pxa/for-next.
> Hi Boris,
> It's targeting 4.15 right now. And we can do as you like, either an immutable
> branch, or I wait to include these patches into my pxa/for-next until you give
> me your go, it's as you like.

Hi Boris,

So what's the status about the sync, should I pick the patches, and have the
others make it to your for-next branch ?



Powered by blists - more mailing lists