From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755426AbbJ1G1N (ORCPT ); Wed, 28 Oct 2015 02:27:13 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:56671 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751290AbbJ1G1L (ORCPT ); Wed, 28 Oct 2015 02:27:11 -0400 Date: Wed, 28 Oct 2015 15:26:54 +0900 From: Darren Hart To: Olof Johansson , Bruce Ashfield Cc: Michal Marek , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, dvhart@linux.intel.com Subject: Re: [PATCH 05/10] merge_config.sh: Better handling of CONFIG_FOO=n Message-ID: <20151028062654.GG1854@malice.jf.intel.com> References: <1445992931-28107-1-git-send-email-olof@lixom.net> <1445992931-28107-6-git-send-email-olof@lixom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1445992931-28107-6-git-send-email-olof@lixom.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 28, 2015 at 09:42:06AM +0900, Olof Johansson wrote: > Kconfig knows how to handle CONFIG_FOO=n just fine, but it'll always > use "# CONFIG FOO is not set" in the resulting config. Mangle the input > accordingly so we don't report this as a failure when it isn't. > > Signed-off-by: Olof Johansson Matching Kconfig behavior is the logical approach, no point in complaining if Kconfig will accpet the result. Bruce, I think we'll just need to update the linux-yocto tool documentation not to mark =n as wrong. Reviewed-by: Darren Hart -- Darren Hart Intel Open Source Technology Center