linux-kernel - Re: [PATCH] staging: speakup: Comparison to NULL could be written

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 for Android: free password hash cracker in your pocket

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

Date:   Sun, 12 Mar 2017 15:29:08 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Arushi Singhal <arushisinghal19971997@...il.com>
Cc:     w.d.hubbs@...il.com, devel@...verdev.osuosl.org,
        Kirk Reiser <kirk@...sers.ca>, speakup@...ux-speakup.org,
        linux-kernel@...r.kernel.org,
        Samuel Thibault <samuel.thibault@...-lyon.org>,
        Chris Brannon <chris@...-brannons.com>
Subject: Re: [PATCH] staging: speakup: Comparison to NULL could be written

On Sat, Mar 11, 2017 at 12:29:09AM +0530, Arushi Singhal wrote:
> Fixed coding style for null comparisons in speakup driver to be more
> consistant with the rest of the kernel coding style.
> 
> Signed-off-by: Arushi Singhal <arushisinghal19971997@...il.com>
> ---
>  drivers/staging/speakup/selection.c   | 2 +-
>  drivers/staging/speakup/varhandlers.c | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)

I have over 25 patches from you for this driver, and I have no idea what
ones I should be applying and in what order.  So I've had to delete them
all from my queue.  Please rebase your series on the latest
staging-testing branch and resend, as a single patch series, what you
wish to have reviewed and potentially applied.

thanks,

greg k-h