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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 4 Apr 2017 10:23:32 +0200
From:   Krzysztof Kozlowski <>
To:     Lee Jones <>
Cc:     Linus Walleij <>,
        Marek Szyprowski <>,
        Sylwester Nawrocki <>,
        Tomasz Figa <>,
        Bartlomiej Zolnierkiewicz <>,
        Chanwoo Choi <>,,,,
Subject: Re: [GIT PULL] mfd: exynos-lpass: Pinctrl dependency

On Mon, Apr 3, 2017 at 12:18 PM, Lee Jones <> wrote:
> On Tue, 28 Mar 2017, Krzysztof Kozlowski wrote:
>> Hi Lee,
>> This is dependency for mfd/exynos-lpass driver changes from Marek Szyprowski.
>> That's a material for v4.12 and I will be pushing this later to Linus Walleij.
> This does not work, and *may* still break.
> The only way to guarantee the order of the patches is to have them
> *all* as part of the pull-request.  Not just some of them.

What do you mean exactly? If these two patches come through my tree
first, then everything will work fine because they do not break any
other stuff.

If you pull it and apply the rest on top, then it should also work
without problems because your history will contain everything needed
in proper order.

In both cases bisectability is preserved. Did I missed something?

Best regards,

Powered by blists - more mailing lists