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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwq-iSOfK2MbWEH3EMyJANqvMTekRwEw6we-vFSMVB2_Q@mail.gmail.com>
Date:   Tue, 15 Nov 2016 08:30:59 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Tomi Valkeinen <tomi.valkeinen@...com>
Cc:     linux-fbdev <linux-fbdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Mathieu Malaterre <malat@...ian.org>
Subject: Re: [GIT PULL] fbdev fixes for 4.9

On Tue, Nov 15, 2016 at 3:40 AM, Tomi Valkeinen <tomi.valkeinen@...com> wrote:
>
> I did test compile, and I would have noticed errors but I missed the warnings
> (I blame the flu...). I need to improve my testing methods, but I couldn't find
> a way to add -Werror to kernel builds. I guess I should just always capture the
> warnings and errors to a file, and check that after the build.
>
> How do you test build?

I basically do just an allmodconfig build, but I do it with

    make -j16 > ../make-output

so that any warnings are very obvious (because stdout goes elsewhere).

              Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ