linux-kernel - Re: [PATCH v3 00/22] Verbatim device names and devm_nvmem

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:   Sun, 25 Feb 2018 19:45:48 -0800
From:   Andrey Smirnov <andrew.smirnov@...il.com>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     Bartosz Golaszewski <brgl@...ev.pl>,
        Heiko Stuebner <heiko@...ech.de>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Carlo Caione <carlo@...one.org>,
        Kevin Hilman <khilman@...libre.com>,
        Matthias Brugger <matthias.bgg@...il.com>,
        Chris Healy <cphealy@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-mediatek@...ts.infradead.org,
        linux-rockchip@...ts.infradead.org,
        linux-amlogic@...ts.infradead.org,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 00/22] Verbatim device names and devm_nvmem_(un)register()

On Thu, Jan 25, 2018 at 1:17 AM, Srinivas Kandagatla
<srinivas.kandagatla@...aro.org> wrote:
>
>
> On 24/01/18 11:13, Bartosz Golaszewski wrote:
>>>
>>>
>> Hi Srinivas,
>>
>> I don't see this series in next - is it going to miss this merge window?
>>
>
> Thanks for your patience.
>
> In general, I pick stuff which are sent before rc5-rc6 and send it to Greg
> KH for inclusion in char-misc tree.
>
> These patches will be queued for next release cycle..
>

Srinivas:

Correct me if I am wrong, but doesn't seem like these patches made it
to char-misc tree yet. I was recently rebasing them on top of Linus'
master and ended up having to resolve a couple of merge conflicts, so
would you like me to re-spin v4 on top of 4.16-rc1 (or any other
version) and re-submit the series?

Thanks,
Andrey Smirnov