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] [day] [month] [year] [list]
Message-ID: <CACRpkdaits4bo4NhdG1Crh2Ds-7q=_WotZeYF6dWMSzFpf-zjQ@mail.gmail.com>
Date:   Thu, 6 Jul 2017 23:52:51 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: add COMPILE_TEST to several drivers

On Tue, Jul 4, 2017 at 5:51 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:

> These drivers are actually platform-agnostic.  Add COMPILE_TEST for
> the compilation test coverage.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>

I had such patches in the past.

It breaks everything to the left and right.

What I need is someone who turns this on PER DRIVER (in their tree)
fixes all the fallout (I don't know how, maybe using 0day builds?), then
sends a patch fixing the fallout and as the last patch turns on
COMPILE_TEST when it doesn't break anything.

And we want to use it for new drivers, ideally.

The arch that always breaks everything us UM Linux.

Yours,
Linus Walleij

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ