From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 8/9] buildman: Propose a format for extra boards
Date: Tue, 12 Nov 2024 20:40:29 -0600 [thread overview]
Message-ID: <20241113024029.GH3600562@bill-the-cat> (raw)
In-Reply-To: <20241108152350.3686274-9-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
On Fri, Nov 08, 2024 at 08:23:49AM -0700, Simon Glass wrote:
> It has become more common to use config fragments to extend or adjust
> the functionality of boards in U-Boot.
>
> Propose a format for how to deal with this. It is not implemented as
> yet.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
I think that the first problem is that this patch series is an
inappropriate method and place to start the discussion.
I also think this gets things backwards as the common case is "make",
not "buildman". We need more defconfig's that are just base +
fragment(s) if they're important enough to be a combination that needs
to be tested and work. A board is not a time-expensive part of CI. A
pytest run is, a new job itself is.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-11-13 2:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:23 [PATCH 0/9] buildman: Add initial support for config fragments Simon Glass
2024-11-08 15:23 ` [PATCH 1/9] buildman: Add a lower-level test for KconfigScanner Simon Glass
2024-11-08 15:23 ` [PATCH 2/9] buildman: Set up the tout library Simon Glass
2024-11-08 15:23 ` [PATCH 3/9] buildman: Support #include files in defconfigs Simon Glass
2024-11-13 2:40 ` Tom Rini
2024-11-13 14:39 ` Simon Glass
2024-11-13 21:53 ` Tom Rini
2024-11-15 14:26 ` Simon Glass
2024-11-15 16:12 ` Tom Rini
2024-11-08 15:23 ` [PATCH 4/9] buildman: Correct the indentation in the setting-up section Simon Glass
2024-11-08 15:23 ` [PATCH 5/9] buildman: Document the toolchain-prefix section Simon Glass
2024-11-08 15:23 ` [PATCH 6/9] buildman: Correct logic for adding a toolchain Simon Glass
2024-11-08 15:23 ` [PATCH 7/9] buildman: Support a tilde to represent the home directory Simon Glass
2024-11-08 15:23 ` [PATCH 8/9] buildman: Propose a format for extra boards Simon Glass
2024-11-09 22:55 ` Heinrich Schuchardt
2024-11-13 2:40 ` Tom Rini [this message]
2024-11-13 16:03 ` Simon Glass
2024-11-13 22:20 ` Tom Rini
2024-11-15 13:37 ` Simon Glass
2024-11-15 14:44 ` Tom Rini
2024-11-17 19:48 ` Simon Glass
2024-11-17 20:52 ` Tom Rini
2024-11-08 15:23 ` [PATCH 9/9] RFC: Show building with #include in defconfig Simon Glass
2024-11-19 22:12 ` (subset) [PATCH 0/9] buildman: Add initial support for config fragments 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=20241113024029.GH3600562@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox