linux-kernel - Re: [PATCH 4/5] ktest: Fix breakage from change of oldnoconfig to olddefconfig

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: <20121213030602.GA10129@adam-station.nay.redhat.com>
Date:	Thu, 13 Dec 2012 11:06:02 +0800
From:	Adam Lee <adam8157@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH 4/5] ktest: Fix breakage from change of oldnoconfig to
 olddefconfig

On Wed, Dec 12, 2012 at 05:14:41PM -0500, Steven Rostedt wrote:
> From: Steven Rostedt <srostedt@...hat.com>
> 
> Commit fb16d891 "kconfig: replace 'oldnoconfig' with 'olddefconfig', and
> keep the old name", changed ktest's default config update from
> oldnoconfig to olddefconfig without adding oldnoconfig as a backup.
> The make oldnoconfig works much better than its backup of:
>    yes '' | make oldconfig
> 
> But due to this change, and the fact that ktest is used to build lots of
> older kernels (and for bisects), it forgoes the oldnoconfig completely.
> 
> Cc: Adam Lee <adam8157@...il.com>
> Cc: Michal Marek <mmarek@...e.cz>
> Signed-off-by: Steven Rostedt <rostedt@...dmis.org>

This makes sense, we should provide a backup for older kernels. Sorry
for not noticing the breakage.

Acked-by: Adam Lee <adam8157@...il.com>

-- 
Regards,
Adam Lee
http://adam8157.info
--
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/