From: Rusty Russell <rusty@rustcorp.com.au>
To: Nicolas Boichat <drinkcat@chromium.org>, linux-kbuild@vger.kernel.org
Cc: Michal Marek <mmarek@suse.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Pranith Kumar <bobby.prani@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Vladimir Murzin <vladimir.murzin@arm.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
John Stultz <john.stultz@linaro.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Quentin Casasnovas <quentin.casasnovas@oracle.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Chris Metcalf <cmetcalf@ezchip.com>, Takashi Iwai <tiwai@suse.de>,
Kyle McMartin <kyle@redhat.com>,
linux-kernel@vger.kernel.org,
Jonathan Kliegman <kliegs@chromium.org>,
olofj@chromium.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2] modpost: Add flag -E for making section mismatches fatal
Date: Tue, 06 Oct 2015 09:45:06 +1030 [thread overview]
Message-ID: <87y4fgnc05.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1443807963-36364-1-git-send-email-drinkcat@chromium.org>
Nicolas Boichat <drinkcat@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.
>
> Setting CONFIG_SECTION_MISMATCH_WARN_ONLY=y causes these warnings to be
> non-fatal, since there are a number of section mismatches when using
> allmodconfig on some architectures, and we do not want to break these
> builds by default.
>
> Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
>
> Change-Id: Ic346706e3297c9f0d790e3552aa94e5cff9897a6
Thanks, applied.
Cheers,
Rusty.
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Nicolas Boichat <drinkcat@chromium.org>, linux-kbuild@vger.kernel.org
Cc: Michal Marek <mmarek@suse.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Pranith Kumar <bobby.prani@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Vladimir Murzin <vladimir.murzin@arm.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
John Stultz <john.stultz@linaro.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Quentin Casasnovas <quentin.casasnovas@oracle.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Chris Metcalf <cmetcalf@ezchip.com>, Takashi Iwai <tiwai@suse.de>,
Nicolas Boichat <drinkcat@chromium.org>,
Kyle McMartin <kyle@redhat.com>,
linux-kernel@vger.kernel.org,
Jonathan Kliegman <kliegs@chromium.org>,
olofj@chromium.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2] modpost: Add flag -E for making section mismatches fatal
Date: Tue, 06 Oct 2015 09:45:06 +1030 [thread overview]
Message-ID: <87y4fgnc05.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1443807963-36364-1-git-send-email-drinkcat@chromium.org>
Nicolas Boichat <drinkcat@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.
>
> Setting CONFIG_SECTION_MISMATCH_WARN_ONLY=y causes these warnings to be
> non-fatal, since there are a number of section mismatches when using
> allmodconfig on some architectures, and we do not want to break these
> builds by default.
>
> Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
>
> Change-Id: Ic346706e3297c9f0d790e3552aa94e5cff9897a6
Thanks, applied.
Cheers,
Rusty.
next prev parent reply other threads:[~2015-10-06 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 17:46 [PATCH v2] modpost: Add flag -E for making section mismatches fatal Nicolas Boichat
2015-10-05 23:15 ` Rusty Russell [this message]
2015-10-05 23:15 ` 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=87y4fgnc05.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=cmetcalf@ezchip.com \
--cc=dave@stgolabs.net \
--cc=drinkcat@chromium.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jan.kiszka@siemens.com \
--cc=john.stultz@linaro.org \
--cc=kliegs@chromium.org \
--cc=kyle@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.com \
--cc=olofj@chromium.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=quentin.casasnovas@oracle.com \
--cc=sam@ravnborg.org \
--cc=tiwai@suse.de \
--cc=vladimir.murzin@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.