linux-kernel - Re: [PATCH v3 2/4] kconfig: regenerate *.c

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]

Date:   Mon, 7 Nov 2016 17:41:38 -0500 (EST)
From:   Nicolas Pitre <nicolas.pitre@...aro.org>
To:     Josh Triplett <josh@...htriplett.org>
cc:     John Stultz <john.stultz@...aro.org>,
        Michal Marek <mmarek@...e.com>,
        Richard Cochran <richardcochran@...il.com>,
        Paul Bolle <pebolle@...cali.nl>,
        Thomas Gleixner <tglx@...utronix.de>,
        Edward Cree <ecree@...arflare.com>, netdev@...r.kernel.org,
        linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/4] kconfig: regenerate *.c_shipped files after
 previous changes

On Mon, 7 Nov 2016, Josh Triplett wrote:

> [snipping large patch]
> 
> One suggestion that might make this patch easier to review: you might
> consider first regenerating the unchanged parser with Bison 3.0.4, then
> regenerating it again after the "imply" change.  I think that'd
> eliminate quite a lot of noise in this patch.

I tried that. This made two large patches instead of just one, both 
equally obscure.

So this patch stands on its own, containing changes that are 
mechanically generated and therefore shouldn't require manual review.


Nicolas