From: Helen Koike <helen@koikeco.de>
To: "Leonardo Brás" <leobras.c@gmail.com>, lkcamp@lists.libreplanetbr.org
Cc: x86@kernel.org, linux-kbuild@vger.kernel.org,
Matthew Wilcox <willy6545@gmail.com>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Michal Marek <michal.lkml@markovi.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Lkcamp] [PATCH 1/4] Adds -Wshadow=local on KBUILD_HOSTCFLAGS
Date: Wed, 17 Oct 2018 01:32:12 -0300 [thread overview]
Message-ID: <716d591a-a0da-e048-a00d-0fe7dabdc4f1@koikeco.de> (raw)
In-Reply-To: <20181017000809.GA21292@WindFlash>
Hi Leonardo,
Thanks for the patch.
On 10/16/18 9:08 PM, Leonardo Brás wrote:
> Adds -Wshadow=local on KBUILD_HOSTCFLAGS to show shadow warnings
> on tools built for HOST.
>
> Signed-off-by: Leonardo Brás <leobras.c@gmail.com>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index e8b599b4dcde..fb0a9ac195e7 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -360,7 +360,7 @@ HOST_LFS_LIBS := $(shell getconf LFS_LIBS 2>/dev/null)
>
> HOSTCC = gcc
> HOSTCXX = g++
> -KBUILD_HOSTCFLAGS := -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 \
> +KBUILD_HOSTCFLAGS := -Wall -Wshadow=local -Wmissing-prototypes -Wstrict-prototypes -O2 \
> -fomit-frame-pointer -std=gnu89 $(HOST_LFS_CFLAGS) \
> $(HOSTCFLAGS)
> KBUILD_HOSTCXXFLAGS := -O2 $(HOST_LFS_CFLAGS) $(HOSTCXXFLAGS)
>
I believe this should be the last patch on this series and not the first
one to avoid commits in between where we have those warnings.
Regards
Helen
next prev parent reply other threads:[~2018-10-17 4:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 0:08 Leonardo Brás
2018-10-17 4:32 ` Helen Koike [this message]
2018-10-17 23:18 ` [Lkcamp] " Leonardo Bras
2018-10-17 8:11 ` Borislav Petkov
2018-10-17 8:21 ` Masahiro Yamada
2018-10-17 8:31 ` Borislav Petkov
2018-10-18 0:40 ` Leonardo Bras
2018-10-18 9:16 ` Borislav Petkov
2018-10-18 16:39 ` Masahiro Yamada
2018-10-18 16:50 ` Borislav Petkov
2018-10-19 2:41 ` Masahiro Yamada
2018-10-19 2:50 ` Leonardo Bras
2018-10-19 8:08 ` Borislav Petkov
2018-10-19 11:28 ` David Laight
2018-10-28 16:54 ` Masahiro Yamada
2018-10-18 0:36 ` Leonardo Bras
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=716d591a-a0da-e048-a00d-0fe7dabdc4f1@koikeco.de \
--to=helen@koikeco.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=leobras.c@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=luto@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=willy6545@gmail.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®