From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: objtool warning breaks build for fs/dlm/lock.o
Date: Fri, 8 May 2020 11:17:50 -0500 [thread overview]
Message-ID: <20200508161750.bl5c7wh36gh6gcvp@treble> (raw)
In-Reply-To: <20200508095509.GX5298@hirez.programming.kicks-ass.net>
On Fri, May 08, 2020 at 11:55:09AM +0200, Peter Zijlstra wrote:
> On Fri, May 08, 2020 at 11:27:39AM +0200, Arnd Bergmann wrote:
>
> > Right, makes sense. It would be nice though to have a way of intentionally
> > turning all objtool warnings into errors. I do my randconfig tests
> > with '-Werror'
> > at the moment in order to catch all new warnings, but this does not catch
> > objtool errors at the moment. For now, this is probably the right thing to do,
> > as there are a couple of warnings that I have no patches for, but at some point
> > I would prefer to trap immediately when a new warning pops up.
>
> Completely untested, and I'm 100% unsure of the Makefile change, but
> something like so, then?
Mostly looks good, but it only errors out on fatal errors, right? For
-Werror (and what Arnd is asking about) should it also return error on
"warnings > 0"?
--
Josh
next prev parent reply other threads:[~2020-05-08 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 14:07 Arnd Bergmann
2020-05-07 23:29 ` Josh Poimboeuf
2020-05-08 9:27 ` Arnd Bergmann
2020-05-08 9:55 ` Peter Zijlstra
2020-05-08 16:17 ` Josh Poimboeuf [this message]
2020-05-08 16:26 ` Peter Zijlstra
2020-05-08 16:29 ` Josh Poimboeuf
2020-05-08 9:45 ` Peter Zijlstra
2020-05-08 16:20 ` Josh Poimboeuf
2020-05-18 19:57 ` Arnd Bergmann
2020-05-18 22:53 ` Josh Poimboeuf
2020-05-18 23:04 ` Josh Poimboeuf
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=20200508161750.bl5c7wh36gh6gcvp@treble \
--to=jpoimboe@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®