linux-kernel - Re: [PATCH v3] kbuild: move extra gcc checks to scripts/Makefile.extrawarn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 16 Apr 2014 23:29:32 +0200
From:	Michal Marek <michal.marek@...fyz.cz>
To:	Masahiro Yamada <yamada.m@...panasonic.com>
Cc:	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
	Michal Marek <mmarek@...e.cz>, Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH v3] kbuild: move extra gcc checks to
 scripts/Makefile.extrawarn

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@...panasonic.com>
> Cc: Michal Marek <mmarek@...e.cz>
> CC: Sam Ravnborg <sam@...nborg.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/