From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Simon Glass <sjg@chromium.org>, u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jaehoon Chung <jh80.chung@samsung.com>,
Jerome Forissier <jerome.forissier@arm.com>,
Kory Maincent <kory.maincent@bootlin.com>,
Kuan-Wei Chiu <visitorckw@gmail.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Marek Vasut <marek.vasut@mailbox.org>,
Marek Vasut <marex@denx.de>, Martin Schwan <m.schwan@phytec.de>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Peng Fan <peng.fan@nxp.com>,
Philip Molloy <philip.molloy@analog.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Raymond Mao <raymond.mao@riscstar.com>,
Stefan Roese <stefan.roese@mailbox.org>,
Tom Rini <trini@konsulko.com>, Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v2 00/11] Move test/py image creation into separate modules
Date: Mon, 08 Jun 2026 09:53:43 +0200 [thread overview]
Message-ID: <87ik7tzcvs.fsf@kernel.org> (raw)
In-Reply-To: <20260523085455.750591-1-sjg@chromium.org>
Hi Simon,
Thank you for the series.
On Sat, May 23, 2026 at 02:54, Simon Glass <sjg@chromium.org> wrote:
> test_ut.py has accumulated a setup_*_image() helper for each image that
> the bootflow tests want to boot. Each one is mostly shell script and
> partition layout, so the file is large and the test logic is hidden
> among image-creation details.
>
> Move each setup function to its own module under test/py/img/, with a
> shared common.py for mkdir_cond(), copy_partition() and the
> make_extlinux_disk() helper. Each patch moves one image at a time so
> reviewers can see the relocation cleanly. The modules are named after
> the bootmeth or feature they exercise rather than the distribution they
> are modelled on.
>
> While here, also redirect the generated disk images to the
> persistent-data directory instead of writing them under the source
> tree. The sandbox mmc, scsi and usb-flash drivers now look there first.
>
> Further improvements are planned, such as using the context manager
> when creating partitions.
I've tested this on sandbox using:
$ ./test/py/test.py --bd sandbox --build -k ut
$ ./test/py/test.py --bd sandbox --build -k bootflow_android
Tested-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
>
prev parent reply other threads:[~2026-06-08 7:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 8:54 [PATCH v2 00/11] Move test/py image creation into separate modules Simon Glass
2026-05-23 8:54 ` [PATCH v2 01/11] test: Create a common file for image utilities Simon Glass
2026-06-08 8:04 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 02/11] test: Move extlinux image-creation to its own file Simon Glass
2026-06-08 8:17 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 03/11] test: Move script " Simon Glass
2026-06-08 8:13 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 04/11] test: Move ChromeOS " Simon Glass
2026-06-08 8:19 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 05/11] test: Move Android " Simon Glass
2026-06-08 8:21 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 06/11] test: Move EFI " Simon Glass
2026-06-08 8:22 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 07/11] test: Move the configuration-editor setup " Simon Glass
2026-06-08 8:23 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 08/11] test: Add Args docstrings to img setup functions Simon Glass
2026-06-08 8:24 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 09/11] test: Reformat line wraps in " Simon Glass
2026-06-08 8:27 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 10/11] sandbox: Find disk images in the persistent-data directory Simon Glass
2026-06-08 8:41 ` Mattijs Korpershoek
2026-05-23 8:54 ` [PATCH v2 11/11] test: Move disk images to " Simon Glass
2026-06-08 8:49 ` Mattijs Korpershoek
2026-06-08 7:53 ` Mattijs Korpershoek [this message]
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=87ik7tzcvs.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=jerome.forissier@arm.com \
--cc=jh80.chung@samsung.com \
--cc=kory.maincent@bootlin.com \
--cc=m.schwan@phytec.de \
--cc=marek.vasut+renesas@mailbox.org \
--cc=marek.vasut@mailbox.org \
--cc=marex@denx.de \
--cc=me@ziyao.cc \
--cc=neil.armstrong@linaro.org \
--cc=peng.fan@nxp.com \
--cc=philip.molloy@analog.com \
--cc=quentin.schulz@cherry.de \
--cc=raymond.mao@riscstar.com \
--cc=sjg@chromium.org \
--cc=stefan.roese@mailbox.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=visitorckw@gmail.com \
--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 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.