linux-kernel - Re: [git pull] drm for v4.7

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+55aFwx6cY45QWVaO2HpSAvbz-bMqC2sFz3+NnKSC4B8xECkg@mail.gmail.com>
Date:	Wed, 25 May 2016 09:13:35 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jani Nikula <jani.nikula@...ux.intel.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	"Bityutskiy, Artem" <artem.bityutskiy@...el.com>
Subject: Re: [git pull] drm for v4.7

On Wed, May 25, 2016 at 1:28 AM, Jani Nikula
<jani.nikula@...ux.intel.com> wrote:
>
> There may be better ones out there, but Artem's "aiaiai" has some
> helpers [1] for diffing build logs, if you want something simple to
> integrate into existing scripts.

It would be lovely to have some kind of warning detection, but quite
frankly, just doing a build and counting lines in 'stderr' from the
build and having some trigger for "oops, lots of new lines" would be
sufficient.

So I don't think anything really fancy to diff build logs is
necessarily needed, although the people who then get the report about
"your merge causes lots of new warnings" might appreciate it.

                Linus