From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cantor2.suse.de ([195.135.220.15]:50123 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752846Ab3ACJGf (ORCPT ); Thu, 3 Jan 2013 04:06:35 -0500 Message-ID: <50E54A14.5010909@suse.cz> Date: Thu, 03 Jan 2013 10:06:28 +0100 From: Michal Marek MIME-Version: 1.0 Subject: Re: [PATCH] modpost: Add flag -f for making section mismatches fatal References: <1356029364-11346-1-git-send-email-kliegs@chromium.org> <87ip7f5ecu.fsf@rustcorp.com.au> In-Reply-To: <87ip7f5ecu.fsf@rustcorp.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Rusty Russell Cc: Jonathan Kliegman , linux-kernel@vger.kernel.org, Greg Kroah-Hartman , Tony Lindgren , linux-kbuild@vger.kernel.org Dne 3.1.2013 00:56, Rusty Russell napsal(a): > Jonathan Kliegman writes: >> The section mismatch warning can be easy to miss during the kernel build >> process. Allow it to be marked as fatal to be easily caught and prevent >> bugs from slipping in. >> >> Signed-off-by: Jonathan Kliegman > > Hmm, a CONFIG option with no Kconfig entry? That seems weird... With a Kconfig entry, all{mod,yes}configs would start failing. It can be enabled with make CONFIG_SECTION_MISMATCH_FATAL=y for now. Maybe it could be added to Kconfig with 'depends on n', so that it is documented somewhere. Michal