All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Aaron Ballman <aaron@aaronballman.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Marco Elver <elver@google.com>,
	clang-built-linux <llvm@lists.linux.dev>,
	Peter Zijlstra <peterz@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	"Jose E. Marchesi" <jemarch@gnu.org>
Subject: Re: Clang/LLVM 'main' regression testing and -Wthread-safety
Date: Thu, 12 Feb 2026 12:01:49 -0500	[thread overview]
Message-ID: <20260212170149.GB1036664@ax162> (raw)
In-Reply-To: <CAAt6xTtmrrZh-+H-jV+bcteZwG1jabraTxWQ-uLJ_N9h1ZLxdA@mail.gmail.com>

On Thu, Feb 12, 2026 at 07:22:26AM -0500, Aaron Ballman wrote:
> On Wed, Feb 11, 2026 at 2:51 PM Nathan Chancellor <nathan@kernel.org> wrote:
> > It has always been on my backburner to try and get a build of the Linux
> > kernel as part of LLVM's continuous integration but I have never had the
> > time to sit down and interface with folks to see what exactly that
> > entails (I figured it would involve integration with LLVM's build bot
> > infrastructure but I have not dug in super hard to the documentation).
> > An arm64 and x86_64 defconfig build would probably catch quite a bit of
> > initial breakage and it would be easy to pin Linux's version and only
> > bump it when thoroughly tested.
> 
> FWIW, I continue to be in full support of adding post-commit CI
> resources for testing Linux kernel needs. I'm not super familiar with
> the infrastructure side of things, but I'm happy to help make
> connections with the folks who do know if it's of help.

Yes, I would greatly appreciate that! I would like to see what it would
entail in full, as I could potentially carve out some time this quarter
or next to actually get it going since it would be beneficial for both
sides.

Cheers,
Nathan

  reply	other threads:[~2026-02-12 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-08 10:02 [GIT PULL] locking updates for v6.20 Ingo Molnar
2026-02-10 22:04 ` pr-tracker-bot
2026-02-11 10:58   ` Clang/LLVM 'main' regression testing and -Wthread-safety Marco Elver
2026-02-11 11:54     ` Miguel Ojeda
2026-02-11 19:51       ` Nathan Chancellor
2026-02-12 12:22         ` Aaron Ballman
2026-02-12 17:01           ` Nathan Chancellor [this message]
2026-02-12 20:03           ` Miguel Ojeda
2026-02-11 19:40     ` Nathan Chancellor
2026-02-11 23:53       ` Marco Elver
2026-02-12 16:57         ` Nathan Chancellor

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=20260212170149.GB1036664@ax162 \
    --to=nathan@kernel.org \
    --cc=aaron@aaronballman.com \
    --cc=bvanassche@acm.org \
    --cc=elver@google.com \
    --cc=jemarch@gnu.org \
    --cc=llvm@lists.linux.dev \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.