workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Tucker <gtucker@gtucker.io>
To: Nathan Chancellor <nathan@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"David Gow" <davidgow@google.com>,
	"Onur Özkan" <work@onurozkan.dev>,
	"Arnd Bergmann" <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	linux-kbuild@vger.kernel.org,
	automated-testing@lists.yoctoproject.org,
	workflows@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3 0/2] scripts: introduce containerized builds
Date: Tue, 20 Jan 2026 10:46:15 +0100	[thread overview]
Message-ID: <4d4ec41f-1203-4cef-8f49-402440f3e983@gtucker.io> (raw)
In-Reply-To: <20260119213516.GA1051134@ax162>

Hi Nathan,

On 19/01/2026 22:35, Nathan Chancellor wrote:
> I went over the script and the documentation and it looks pretty good to
> me at this point. My only comment would be potentially referencing the
> TuxMake container images in the example section to give folks a
> "prebuilt" container option while getting the kernel.org container
> images sorted out but that can always be done in a follow-up change.

Well the tuxmake LLVM image is mentioned in the first example:

    scripts/container -i tuxmake/korg-clang -- make LLVM=1 defconfig
    scripts/container -i tuxmake/korg-clang -- make LLVM=1 -j$(nproc)

So that should just work out of the box.  Or did you mean to add
something else to the docs?

But yes, the topic of available container images will be something to
expand upon once the tool starts getting used.  If things go well
with this initial version then we can try and move forward with
hosting first-party images as per the other discussion thread:

    https://lore.kernel.org/all/cc737636-2a43-4a97-975e-4725733f7ee4@gtucker.io/

> I will apply this to kbuild-next-unstable shortly to give folks a week
> or so to voice any objections or give critical review comments.

Sounds great, thanks!  I'll spread the word too once it's available
in linux-next.

Cheers,
Guillaume


  parent reply	other threads:[~2026-01-20  9:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31 16:51 Guillaume Tucker
2025-12-31 16:51 ` [PATCH v3 1/2] scripts: add tool to run " Guillaume Tucker
2025-12-31 16:51 ` [PATCH v3 2/2] Documentation: dev-tools: add container.rst page Guillaume Tucker
2026-01-20 13:53   ` Nicolas Schier
2026-01-20 18:35     ` Nathan Chancellor
2026-01-20 18:39       ` Nathan Chancellor
2026-01-21  9:55       ` Guillaume Tucker
2026-01-22  4:55         ` Nathan Chancellor
2026-01-22 14:25           ` Guillaume Tucker
2026-01-22 10:13     ` Guillaume Tucker
2026-01-16 10:28 ` [PATCH v3 0/2] scripts: introduce containerized builds Guillaume Tucker
2026-01-16 21:12   ` Nathan Chancellor
2026-01-19 14:22     ` Guillaume Tucker
2026-01-19 21:35 ` Nathan Chancellor
2026-01-19 21:49   ` Nathan Chancellor
2026-01-20  9:56     ` Guillaume Tucker
2026-01-20 17:58       ` Nathan Chancellor
2026-01-20  9:46   ` Guillaume Tucker [this message]
2026-01-20 17:55     ` Nathan Chancellor
2026-01-20 13:54 ` Nicolas Schier
2026-01-20 18:04   ` Nathan Chancellor
2026-01-21 10:13   ` Guillaume Tucker
2026-01-22 14:12   ` Guillaume Tucker
2026-01-27 20:13     ` Nicolas Schier
2026-01-31 13:36       ` Guillaume Tucker

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=4d4ec41f-1203-4cef-8f49-402440f3e983@gtucker.io \
    --to=gtucker@gtucker.io \
    --cc=arnd@arndb.de \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=davidgow@google.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.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