From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Brandon Maier <brandon.maier@collins.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jerome Forissier <jerome.forissier@linaro.org>,
Neha Malcom Francis <n-francis@ti.com>,
Sumit Garg <sumit.garg@linaro.org>
Subject: [PATCH 0/9] buildman: Add initial support for config fragments
Date: Fri, 8 Nov 2024 08:23:41 -0700 [thread overview]
Message-ID: <20241108152350.3686274-1-sjg@chromium.org> (raw)
This series updates buildman to process #include lines in defconfig
files. With this, it is no-longer necessary to duplicate lines certain
lines from the include-file in the defconfig, e.g. CONFIG_ARM and
CONFIG_SOC_...
Simon Glass (9):
buildman: Add a lower-level test for KconfigScanner
buildman: Set up the tout library
buildman: Support #include files in defconfigs
buildman: Correct the indentation in the setting-up section
buildman: Document the toolchain-prefix section
buildman: Correct logic for adding a toolchain
buildman: Support a tilde to represent the home directory
buildman: Propose a format for extra boards
RFC: Show building with #include in defconfig
configs/j721e_sk_a72_defconfig | 5 --
tools/buildman/boards.py | 25 +++++++-
tools/buildman/buildman.rst | 102 ++++++++++++++++++++++++++++-----
tools/buildman/func_test.py | 85 +++++++++++++++++++++++++++
tools/buildman/main.py | 9 ++-
tools/buildman/test.py | 50 ++++++++++++++++
tools/buildman/toolchain.py | 47 ++++++++-------
7 files changed, 281 insertions(+), 42 deletions(-)
--
2.34.1
next reply other threads:[~2024-11-08 15:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:23 Simon Glass [this message]
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
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=20241108152350.3686274-1-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=andrejs.cainikovs@toradex.com \
--cc=brandon.maier@collins.com \
--cc=jerome.forissier@linaro.org \
--cc=n-francis@ti.com \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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