linux-kernel - Re: [PATCH] gpio-hammer: Avoid potential overflow in main

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

Message-ID: <CAMpxmJVSPA9CQBGULyk69KaP42oMdKGg883z0FeFC_mSA5w2xA@mail.gmail.com>
Date:   Thu, 12 Mar 2020 15:29:57 +0100
From:   Bartosz Golaszewski <bgolaszewski@...libre.com>
To:     Gabriel Ravier <gabravier@...il.com>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        linux-gpio <linux-gpio@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio-hammer: Avoid potential overflow in main

czw., 12 mar 2020 o 15:21 Gabriel Ravier <gabravier@...il.com> napisał(a):
>
> Ah, that was accidental. I was applying scripts/Lindent to my code and
> ended up also having it applied to part of the old code. Didn't think it
> would hurt, but I guess it makes sense to be this stringent on
> separating logical changes. Will send a (complete) corrected patch
> in-reply-to this message.
>

Please don't send patches in response to other threads. Always start a
new thread and increment the version in [PATCH vX] tag.

Bart