From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v1 1/1] Makefile.extrawarn: Turn off -Werror when extra warnings are enabled
Date: Fri, 25 Mar 2022 16:53:41 +0200 [thread overview]
Message-ID: <Yj3XdSYyxfv5/Al8@smile.fi.intel.com> (raw)
In-Reply-To: <CAK7LNAR9HS7LK5D-07i8_tFcwd=uiHEFu05n0t_UuFZExcfBpw@mail.gmail.com>
On Fri, Mar 25, 2022 at 11:34:06PM +0900, Masahiro Yamada wrote:
> On Fri, Mar 25, 2022 at 10:13 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > When `make W=1 ...` is executed the level 1 warnings become errors,
> > due to recent change in some of the defconfigs, and fail the build.
> > Since there are a lot of warnings on the level 1 are still present
> > in the defconfigs at least for x86, let disable -Werror in such case.
>
>
> commit b339ec9c229aaf399296a120d7be0e34fbc355ca
> made WERROR default to COMPILE_TEST.
>
> WERROR should not be enabled for regular builds.
>
> b9080ba4a6ec should be reverted.
Hmm... works for me, but have you read this discussion:
https://lore.kernel.org/r/YjsCpoRK7W4l6tSh@zn.tnic
?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-25 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 13:13 [PATCH v1 1/1] Makefile.extrawarn: Turn off -Werror when extra warnings are enabled Andy Shevchenko
2022-03-25 14:34 ` Masahiro Yamada
2022-03-25 14:53 ` Andy Shevchenko [this message]
2022-03-25 17:20 ` Linus Torvalds
2022-03-25 17:18 ` Linus Torvalds
2022-03-25 17:51 ` Andy Shevchenko
2022-03-25 20:01 ` kernel test robot
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=Yj3XdSYyxfv5/Al8@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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