workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: "Ben Copeland" <ben.copeland@linaro.org>,
	"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nsc@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Onur Özkan" <work@onurozkan.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	workflows@vger.kernel.org,
	automated-testing@lists.yoctoproject.org,
	"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Subject: Re: Hosting first-party kernel.org container images
Date: Thu, 19 Mar 2026 12:10:19 +0100	[thread overview]
Message-ID: <CANiq72=t=q4__vwTFjg+gQyjKLUEJrZBngr3cAnnKiTNM5uteg@mail.gmail.com> (raw)
In-Reply-To: <78adef0e-81b0-47d4-be20-32f42ab8ec04@gtucker.io>

On Wed, Feb 25, 2026 at 3:44 PM Guillaume Tucker <gtucker@gtucker.io> wrote:
>
> Nathan, Nicolas, Miguel - what are your thoughts on this?

I agree with Nathan that `Containerfile`s on git.kernel.org sounds good.

While many kernel developers may not use them (mostly because everyone
has their own setup already), if we had a set of "base" images that
are maintained by someone trusted (including publishing them in the
usual registries for easy use), then I think a bunch of us would
actually use them for CI and possibly other tasks; just like some of
us already use the kernel.org toolchains "manually" anyway etc.

It could serve as an entry point to discover the different toolchains
and software offered by kernel.org, i.e. not just the GCC and LLVM and
LLVM+Rust toolchains, but also perhaps `b4` pre-installed and so on.
Even things like `tc-build` or the latest and greatest set of AI
context text files could be considered too.

It could also perhaps simplify a tiny bit giving quick reproducers
compared to giving the instructions for a distro base image + extra
things to install. It could also be a good thing to give newcomers
(i.e. how to set up all the development environment is a common
question) and LLMs.

I mean, all this is nothing new of course, but sometimes trust and
convenience go a long way.

I hope that helps!

Cheers,
Miguel

  parent reply	other threads:[~2026-03-19 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 13:37 Guillaume Tucker
2026-02-02 12:07 ` Ben Copeland
2026-02-25 14:44   ` Guillaume Tucker
2026-03-10  0:48     ` Nathan Chancellor
2026-03-19 10:37       ` Guillaume Tucker
2026-03-19 11:10     ` Miguel Ojeda [this message]
2026-03-19 14:15       ` Theodore Tso

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='CANiq72=t=q4__vwTFjg+gQyjKLUEJrZBngr3cAnnKiTNM5uteg@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=arnd@arndb.de \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=ben.copeland@linaro.org \
    --cc=gtucker@gtucker.io \
    --cc=kernelci@lists.linux.dev \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=work@onurozkan.dev \
    --cc=workflows@vger.kernel.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