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] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Dec 2017 12:55:34 +0100
From:   Greg KH <>
To:     Tomas Marek <>
Subject: Re: [PATCH v3] Staging: pi433: fix brace coding style issues in

On Sat, Dec 09, 2017 at 12:41:11PM -0800, Tomas Marek wrote:
> This patch fix several brace on next line, braces not necessary, space
> around =/<, and space before/after open/close parenthesis coding style
> errors find by checkpatch in pi433_if.c.
> Signed-off-by: Tomas Marek <>
> ---
> Changes in v3:
>   - DIO0_irq_handler update reverted - will be submitted in separate
>     patch for the sake of clarity.
> Changes in v2:
>   - DIO0_irq_handler updated - 'if/else if' replaced by 'switch' and
>     'dev_dbg_ratelimited' used instead of 'dev_dbg' according to Joe
>     Perches suggestion.
>   - The removal of braces around SET_CHECKED() reverted - caused syntax
>     error and is addressed by another patch
>     "[PATCHv2] staging: pi433: pi433_if.c remove SET_CHECKED macro".

This doesn't apply to my tree at all :(

Please rebase it against the staging-next branch of staging.git (or the
staging-testing branch to be sure), and then resend.


greg k-h

Powered by blists - more mailing lists