From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kbuild: re-enable int-in-bool-context warning
Date: Mon, 13 May 2019 11:26:12 +0900 [thread overview]
Message-ID: <CAK7LNARrrJD-7j-P8===Y4ZG5_--=35QQ4R1HALkvUZE_BO1Ow@mail.gmail.com> (raw)
In-Reply-To: <1557363481-27178-1-git-send-email-yamada.masahiro@socionext.com>
On Thu, May 9, 2019 at 9:58 AM Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
>
> This warning was disabled by commit bd664f6b3e37 ("disable new
> gcc-7.1.1 warnings for now") just because it was too noisy.
>
> Thanks to Arnd Bergmann, all warnings have been fixed. Now, we are
> ready to re-enable it.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> ---
Applied to linux-kbuild.
> Changes in v2:
> - rebase
>
> Makefile | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index a61a95b..2896518 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -692,7 +692,6 @@ KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks,)
> KBUILD_CFLAGS += $(call cc-disable-warning,frame-address,)
> KBUILD_CFLAGS += $(call cc-disable-warning, format-truncation)
> KBUILD_CFLAGS += $(call cc-disable-warning, format-overflow)
> -KBUILD_CFLAGS += $(call cc-disable-warning, int-in-bool-context)
> KBUILD_CFLAGS += $(call cc-disable-warning, address-of-packed-member)
>
> ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
> --
> 2.7.4
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2019-05-13 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 0:58 [PATCH v2] kbuild: re-enable int-in-bool-context warning Masahiro Yamada
2019-05-13 2:26 ` Masahiro Yamada [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='CAK7LNARrrJD-7j-P8===Y4ZG5_--=35QQ4R1HALkvUZE_BO1Ow@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
/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;
as well as URLs for NNTP newsgroup(s).