Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Philip Li <philip.li@intel.com>, lkp@intel.com
Cc: llvm@lists.linux.dev, peterz@infradead.org, jpoimboe@kernel.org
Subject: Removing LLVM objtool warning filter
Date: Fri, 20 Dec 2024 13:06:17 -0700	[thread overview]
Message-ID: <20241220200617.GA936171@ax162> (raw)

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?

Cheers,
Nathan

             reply	other threads:[~2024-12-20 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 20:06 Nathan Chancellor [this message]
2024-12-21  0:33 ` Removing LLVM objtool warning filter Philip Li
2024-12-23 21:34   ` Nathan Chancellor
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=20241220200617.GA936171@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