mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Jonathan Kliegman <kliegs@chromium.org>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tony Lindgren <tony@atomide.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] modpost: Add flag -f for making section mismatches fatal
Date: Thu, 03 Jan 2013 10:06:28 +0100	[thread overview]
Message-ID: <50E54A14.5010909@suse.cz> (raw)
In-Reply-To: <87ip7f5ecu.fsf@rustcorp.com.au>

Dne 3.1.2013 00:56, Rusty Russell napsal(a):
> Jonathan Kliegman <kliegs@chromium.org> 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 <kliegs@chromium.org>
> 
> 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

  reply	other threads:[~2013-01-03  9:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 18:49 Jonathan Kliegman
2013-01-02 23:56 ` Rusty Russell
2013-01-03  9:06   ` Michal Marek [this message]
2013-01-03 21:39     ` Jonathan Kliegman
2013-01-12 21:24       ` Michal Marek
2013-01-06  9:36 ` Sam Ravnborg
2013-01-06 20:22   ` Jonathan Kliegman
2013-01-08 19:16     ` Sam Ravnborg
2013-01-08 19:38       ` Jonathan Kliegman
2013-01-08 19:39         ` Sam Ravnborg
2015-10-02  0:34 Nicolas Boichat
2015-10-02  1:26 ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50E54A14.5010909@suse.cz \
    --to=mmarek@suse.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=kliegs@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome