From: Marek Vasut <marek.vasut@mailbox.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Jerome Forissier <jerome.forissier@linaro.org>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 1/3] test: env: Add test for environment storage in SPI NOR
Date: Tue, 23 Dec 2025 19:55:45 +0100 [thread overview]
Message-ID: <bb3d1ff2-4cc1-48da-a47f-3aef44277791@mailbox.org> (raw)
In-Reply-To: <c31bd8b3-2604-4193-abba-6815845e8967@gmx.de>
On 12/23/25 6:32 PM, Heinrich Schuchardt wrote:
> On 12/23/25 15:31, Marek Vasut wrote:
>> Add test for environment stored in SPI NOR. The test works in a very
>> similar way to the current test for environment stored in ext4 FS,
>> except it generates spi.bin file backing the SPI NOR.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
>> ---
>> Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
>> Cc: Jerome Forissier <jerome.forissier@linaro.org>
>> Cc: Simon Glass <sjg@chromium.org>
>> Cc: Tom Rini <trini@konsulko.com>
>> Cc: u-boot@lists.denx.de
>> ---
>> V2: No change
>> ---
>> test/py/tests/test_env.py | 99 +++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 99 insertions(+)
>>
>> diff --git a/test/py/tests/test_env.py b/test/py/tests/test_env.py
>> index 383e26c03b0..48e31f19b3c 100644
>> --- a/test/py/tests/test_env.py
>> +++ b/test/py/tests/test_env.py
>> @@ -457,6 +457,26 @@ def mk_env_ext4(state_test_env):
>> utils.run_and_log(c, ['cp', '-f', persistent, fs_img])
>> return fs_img
>> +def mk_env_spi_flash(state_test_env):
>
> Thank you for adding the test.
>
> Unfortunately pylint doesn't like your code. Please have a look.
Is this something we run in CI ? If so, CI builds did pass.
If not, how do I trigger this ?
next prev parent reply other threads:[~2025-12-23 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 14:31 [PATCH v2 1/3] test: env: Add test for environment storage in SPI NOR Marek Vasut
2025-12-23 14:31 ` [PATCH v2 2/3] env: Add single to redundant environment upgrade path Marek Vasut
2025-12-23 17:43 ` Heinrich Schuchardt
2025-12-23 18:04 ` Tom Rini
2025-12-23 18:53 ` Marek Vasut
2025-12-23 14:31 ` [PATCH v2 3/3] configs: sandbox: Enable environment in SPI NOR support Marek Vasut
2025-12-23 17:58 ` Heinrich Schuchardt
2025-12-23 18:07 ` Tom Rini
2025-12-23 17:32 ` [PATCH v2 1/3] test: env: Add test for environment storage in SPI NOR Heinrich Schuchardt
2025-12-23 18:55 ` Marek Vasut [this message]
2025-12-23 23:32 ` Tom Rini
2025-12-31 16:07 ` Marek Vasut
2025-12-31 16:11 ` Tom Rini
2025-12-31 16:50 ` Marek Vasut
2025-12-31 17:18 ` Tom Rini
2025-12-31 17:46 ` Marek Vasut
2025-12-24 3:18 ` Heinrich Schuchardt
2026-01-07 21:06 ` 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=bb3d1ff2-4cc1-48da-a47f-3aef44277791@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=jerome.forissier@linaro.org \
--cc=sjg@chromium.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