[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250207214113.GB661404@ax162>
Date: Fri, 7 Feb 2025 14:41:13 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: Brendan Jackman <jackmanb@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Nicolas Schier <nicolas@...sle.eu>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH v3 0/2] objtool: Add option to fail build on vmlinux
warnings
On Thu, Feb 06, 2025 at 06:51:27PM -0800, Josh Poimboeuf wrote:
> On Thu, Feb 06, 2025 at 10:10:36AM -0700, Nathan Chancellor wrote:
> > Right, I think gating on '!COMPILE_TEST' would not be a terrible way to
> > introduce it. We would definitely want to remove that dependency as
> > soon as possible because we want compile testers to be qble to find
> > these problems and have them be noticeable but it should make the
> > introduction of CONFIG_OBJTOOL_WERROR less disruptive.
>
> I want to get CONFIG_OBJTOOL_WERROR merged soon. I'm working on some
> other patches to go along with it that will hopefully ease some of the
> pain. I'll post those soon and then hopefully we can get it into
> linux-next.
Sounds good to me, getting it into linux-next will give us a good idea
of how disruptive it may be.
> I didn't quite follow the OBJTOOL_FLAGS idea. We already have
> OBJTOOL_ARGS which allows adding arguments (though not removing them),
> was it mean to be something like that?
Yes, I should have prefaced "if it does not already exist" since I did
not realize that there was already support for adding to objtool
arguments via an environment/make variable already.
Cheers,
Nathan
Powered by blists - more mailing lists