From: Nathan Chancellor <nathan@kernel.org>
To: Philip Li <philip.li@intel.com>
Cc: lkp@intel.com, llvm@lists.linux.dev, peterz@infradead.org,
jpoimboe@kernel.org
Subject: Re: Removing LLVM objtool warning filter
Date: Mon, 23 Dec 2024 14:34:47 -0700 [thread overview]
Message-ID: <20241223213447.GA1188382@ax162> (raw)
In-Reply-To: <Z2YMxZtiHCV5+w9H@rli9-mobl>
Hi Philip,
On Sat, Dec 21, 2024 at 08:33:09AM +0800, Philip Li wrote:
> On Fri, Dec 20, 2024 at 01:06:17PM -0700, Nathan Chancellor wrote:
> > Hi Philip and other LKP folks,
> >
> > At some point, I believe there was a filter set up so that reports of
> > objtool warnings that appear in clang builds were sent only to our
> > mailing list (llvm@lists.linux.dev) for triage. At this point, we
> > believe it is best to treat those reports like other objtool reports and
> > send them to the author of the change that introduced the warning with
> > our list on CC in case people think it is a compiler bug or need further
> > help understanding what is going on. Is that possible?
>
> Got it Nathan, I will update the bot to send out this warning to author
> and cc llvm list, same as other warnings from clang.
Thanks a lot!
> Just to confirm, is it applied to all clang version or only latest one
> like clang 19/20?
Let's do all clang versions and see how noisy it is. If we need to scale
it back to just the latest, we can definitely do so.
Cheers,
Nathan
next prev parent reply other threads:[~2024-12-23 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 20:06 Removing LLVM objtool warning filter Nathan Chancellor
2024-12-21 0:33 ` Philip Li
2024-12-23 21:34 ` Nathan Chancellor [this message]
2024-12-24 0:28 ` Philip Li
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=20241223213447.GA1188382@ax162 \
--to=nathan@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=philip.li@intel.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