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  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:   Sat, 15 Aug 2020 08:16:20 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL v2] MFD for v5.9

On Fri, Aug 14, 2020 at 7:42 AM Lee Jones <lee.jones@...aro.org> wrote:
>
> Here is the new pull request.  It has been tested; locally, by
> TuxBuild and the Intel 'kernel test robot' [0].  Please consider this for
> addition into v5.9.  All of these patches have also soak tested in
> -next for a considerable amount of time.

I'm extremely annoyed by this all, but I've pulled this.

Please just *STOP* doing any W=1 fixes (and most definitely W=2 ones -
many of those warnings are just plain garbage and indicate more about
the compiler than they do about the code) if you can't then make damn
sure that the warnings that actually matter are always *ALWAY* taken
care of.

I absolutely abhor warnings in the default build, just because they
only result in people ignoring them. Which is exactly what happened
bvecause you then tried to care about the more-or-less worthless W=1
ones.

So a clean build is really important to me. And developers who don't
check and follow up on warnings in the normal build are something that
pisses me off no end.

Now something like 25 commits are pointlessly rebased just because you
didn't check warnings properly.

                     Linus

Powered by blists - more mailing lists