From: Michal Marek <michal.marek@matfyz.cz>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v3] kbuild: move extra gcc checks to scripts/Makefile.extrawarn
Date: Wed, 16 Apr 2014 23:29:32 +0200 [thread overview]
Message-ID: <20140416212932.GC20810@fiji.localdomain> (raw)
In-Reply-To: <1397467630-16727-1-git-send-email-yamada.m@jp.panasonic.com>
On Mon, Apr 14, 2014 at 06:27:10PM +0900, Masahiro Yamada wrote:
> W=... provides extra gcc checks.
>
> Having such code in scripts/Makefile.build results in the same flags
> being added to KBUILD_CFLAGS multiple times becuase
> scripts/Makefile.build is invoked every time Kbuild descends into
> the subdirectories.
>
> Since the top Makefile is already too cluttered, this commit moves
> all of extra gcc check stuff to a new file scripts/Makefile.extrawarn,
> which is included from the top Makefile.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: Michal Marek <mmarek@suse.cz>
> CC: Sam Ravnborg <sam@ravnborg.org>
> ---
>
> Changes in v3:
> - Rebase on v3.15-rc1
> (v2 caused a conflict with Clang stuff.)
>
> Changes in v2:
> - Move the code to a new file scripts/Makefile.extrawarn
> - Move also "KBUILD_ENABLE_EXTRA_GCC_CHECKS" definition
Applied to kbuild.git#kbuild, thanks.
Michal
prev parent reply other threads:[~2014-04-16 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 9:27 [PATCH v3] kbuild: move extra gcc checks to scripts/Makefile.extrawarn Masahiro Yamada
2014-04-16 21:29 ` Michal Marek [this message]
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=20140416212932.GC20810@fiji.localdomain \
--to=michal.marek@matfyz.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=yamada.m@jp.panasonic.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