From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
U-Boot Custodians <u-boot-custodians@lists.denx.de>
Subject: Re: In-tree Python tools (patman, buildman, binman, etc.)
Date: Tue, 05 May 2026 11:00:50 +0200 [thread overview]
Message-ID: <87qznqcjst.fsf@kernel.org> (raw)
In-Reply-To: <20260504160645.GF1614990@bill-the-cat>
Hi Simon,
On Mon, May 04, 2026 at 10:06, Tom Rini <trini@konsulko.com> wrote:
> On Mon, May 04, 2026 at 06:16:58AM -0600, Simon Glass wrote:
>> Hi,
>>
>> As you know, I maintain several tools which are part of the U-Boot tree.
>>
>> Tom has previously suggested that it would be better to move patman
>> out of the U-Boot tree, e.g. to its own Github project. It is a
>> general tool which can be used with Linux and other
>> mailing-list/patchwork-based projects. I have never been keen on
>> taking on the extra effort required, but I've recently added more
>> features and am wondering whether now might be a good time to do this.
>>
>> Buildman is quite obviously designed specifically for U-Boot. I have
>> made some improvements recently (a large code refactor and distributed
>> builds). I would like to push those changes to mainline. Do people
>> think it should be in a separate tree somewhere?
>>
>> Binman was written with U-Boot in mind but supports other projects
>> (such as Zephyr). It is generic enough that it could be separated. The
>> impact would be harder code review.
>>
>> We also have smaller things like qconfig (which I have substantially
>> rewritten to make it fast) and dtoc, which is very tailored to U-Boot.
>>
>> What do people think? Of all of these, patman would be the easiest to
>> move, with the least impact on existing workflows.
First, thanks for maintaining those tools. I'm not an user of all of
them but I think they are great. Especially binman and buildman.
>
> Given that as a project we've been encouraging people to switch to using
> "b4" as it's now widely used and covers many of the problems patman was
> designed to solve, I think that's an easy one to say that you should
> move to your own personal hosting somewhere and it be untied from the
> project. The rest of the tools are something we as a community can
> figure out how to address once some of our general infrastructure issues
> are unblocked and moving forward.
I agree with Tom here. I think that moving patman out of the U-Boot tree
is a good choice. Personally, I'm a happy b4 user so I've never tried
patman.
Let's start ("small") with moving patman and see how things go from there?
>
> --
> Tom
next prev parent reply other threads:[~2026-05-05 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 12:16 In-tree Python tools (patman, buildman, binman, etc.) Simon Glass
2026-05-04 16:06 ` Tom Rini
2026-05-05 9:00 ` Mattijs Korpershoek [this message]
2026-05-08 10:05 ` Quentin Schulz
2026-05-15 20:57 ` Simon Glass
2026-05-15 21:54 ` Greg Malysa
2026-05-19 7:52 ` Neha Malcom Francis
2026-05-21 0:38 ` Simon Glass
2026-05-22 18:00 ` Tom Rini
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=87qznqcjst.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
/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.