linux-kernel - Re: [PATCH v2 1/3] binder: fix sparse warnings on locking context

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] [day] [month] [year] [list]

Message-ID: <CAHRSSExoDxyJNnxgWEbb_yM1ff5Rvf-5fhFSsXNqDVa7FPHrnA@mail.gmail.com>
Date:   Fri, 7 Dec 2018 08:25:35 -0800
From:   Todd Kjos <tkjos@...gle.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     "open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
        Todd Kjos <tkjos@...roid.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Arve Hjønnevåg <arve@...roid.com>,
        Martijn Coenen <maco@...gle.com>, joel@...lfernandes.org,
        Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH v2 1/3] binder: fix sparse warnings on locking context

On Thu, Dec 6, 2018 at 11:08 PM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
...
> But I thought I applied this back on November 26:
>         https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/commit/?h=char-misc-testing&id=324fa64cf4189094bc4df744a9e7214a1b81d845
>
> You should have gotten an email from my scripts at that time.
>
> or is this somehow a different patch with the same commit log?
> Or a v2 that changed from the one that I had applied?  Do I need to
> revert this one and apply your new one?

Sorry, you are right, you already applied it. I was thrown off by a
subsequent mail (https://lkml.org/lkml/2018/12/5/1042) in which you
said "Ok, no need for numbering them, but they do need to be resent
based on the feedback I gave.  I've dropped them all from my queue
because of that.".

So I thought it had been dropped. Anyway, glad its there and no need
for further action on it.

-Todd