From: Nathan Chancellor <nathan@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
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 2/2] Documentation: dev-tools: add container.rst page
Date: Wed, 21 Jan 2026 21:55:34 -0700 [thread overview]
Message-ID: <20260122045534.GA3770486@ax162> (raw)
In-Reply-To: <e96a6e71-80b3-4556-a4eb-fd242e0f5713@gtucker.io>
On Wed, Jan 21, 2026 at 10:55:53AM +0100, Guillaume Tucker wrote:
> Feel free to make these tweaks now, or we might wait a bit to see if
> others have more feedback with further changes and I can send a v4.
How about this? Send a v4 with:
1. An initial MAINTAINERS entry addition in patch 1 for
scripts/container like I suggested earlier and scripts/container
explicitly added to the KERNEL BUILD section so that Nicolas and I
are included for handling patches.
2. Add the Documentation to the aforementioned MAINTAINERS entry as part
of patch 2.
3. Either encorporate my suggested change for preferring podman over
docker with the appropriate changes elsewhere inte the patch set like
you mentioned or explore checking for the docker alias explicitly.
Entirely up to you timewise, as long as it results in Nicolas's
environment working, since I don't think that will be too uncommon.
4. Encorporate any other feedback that you feel is appropriate at this
stage (if there is any low hanging fruit).
Then we can apply it so that folks can start using it in -next for
testing and validation. After that, you can start thinking of things you
would want to work on for future merge windows from the list you already
started, as I know how that goes when working on a new tool :)
Cheers,
Nathan
next prev parent reply other threads:[~2026-01-22 4:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 16:51 [PATCH v3 0/2] scripts: introduce containerized builds 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 [this message]
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
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=20260122045534.GA3770486@ax162 \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=automated-testing@lists.yoctoproject.org \
--cc=davidgow@google.com \
--cc=gtucker@gtucker.io \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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