linux-kernel - Re: [PATCH] merge_config.sh: Use the first file as the initial config

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: <20120324222649.GB8947@sepie.suse.cz>
Date:	Sat, 24 Mar 2012 23:26:49 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	John Stultz <john.stultz@...aro.org>,
	kernel-team@...oraproject.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] merge_config.sh: Use the first file as the initial config

On Wed, Feb 01, 2012 at 12:01:58PM -0500, Josh Boyer wrote:
> Take the first config fragment and use it verbatim as the initial config set.
> This avoids running the verification loop for the first file, as nothing has
> actually been merged at this point.  This significantly increases performance
> for large config fragments.
> 
> Signed-off-by: Josh Boyer <jwboyer@...hat.com>

Applied to kbuild.git#kconfig, thanks.

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/