Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: SJ Park <sj@kernel.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Miguel Ojeda <ojeda@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: kernel.org container images
Date: Thu, 15 Oct 2026 06:36:37 -0700	[thread overview]
Message-ID: <20261015133638.86959-1-sj@kernel.org> (raw)
In-Reply-To: <01a87de4-8de5-4ff0-941b-2e5932a3a19c@gtucker.io>

On Mon, 28 Sep 2026 14:30:48 +0200 Guillaume Tucker <gtucker@gtucker.io> wrote:

> Hello,
> 
> We discussed the topic of managing container images on kernel.org
> again at Kernel Recipes last week with Konstantin and Arnd.  The
> idea is to provide a set of reference images with kernel.org
> toolchains which developers could use via the scripts/container
> tool.  They would provide a common denominator to facilitate
> development and reproducibility.  These images would of course not
> be tied to any single tool and could provide a basis for CI bots
> such as KernelCI or tuxmake.

I run a few humble and hacky build tests on my local machine.  I also want to
do the build test on more setups including rust enabled build, and on more
machines of different architectures.  But I'm short of time to learn how to do
cross build correctly.  The Rust for Linux training at LPC helped me doing rust
enabled kernel build for the first time, though.  Kudos to Rust for Linux team.

I am therefore considering options including use of the scripts/container tool.
I was unable to find a time to do that so far, though.  Having recommended
images in kernel.org will definitly help me prioritizing it.

I also find opportunities to use the images not only for build tests but more
use cases including benchmark runs.

I just wanted to say thank you for developing the tool and this kernel.org
registry initiative.  Looking forward to more progress, and I will also try to
find if there is something that I can help.


Thanks,
SJ

[...]

      reply	other threads:[~2026-10-15 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 12:30 kernel.org container images Guillaume Tucker
2026-10-15 13:36 ` SJ Park [this message]

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=20261015133638.86959-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gtucker@gtucker.io \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --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