From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
u-boot@lists.denx.de,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: Re: [PATCH 1/1] doc: describe u-boot-test-release
Date: Mon, 05 May 2025 12:04:38 +0200 [thread overview]
Message-ID: <871pt374qx.fsf@kernel.org> (raw)
In-Reply-To: <20250503101424.48236-1-heinrich.schuchardt@canonical.com>
Hi Heinrich,
Thank you for the patch.
On sam., mai 03, 2025 at 12:14, Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:
> The scripts u-boot-test-release is called at the end of testing.
> Describe it.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> ---
> doc/develop/py_testing.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/develop/py_testing.rst b/doc/develop/py_testing.rst
> index 217ae447035..824e3c0d9a7 100644
> --- a/doc/develop/py_testing.rst
> +++ b/doc/develop/py_testing.rst
> @@ -388,6 +388,13 @@ to download the U-Boot binary directly into RAM and execute it. This would
> avoid the need for `u-boot-test-flash` to actually write U-Boot to flash, thus
> saving wear on the flash chip(s).
>
> +u-boot-test-release
> +'''''''''''''''''''
> +
> +When all tests for the board have been executed, this script is called.
> +
> +The board can be switched off now.
> +
> Examples
> ''''''''
>
> --
> 2.48.1
prev parent reply other threads:[~2025-05-05 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 10:14 [PATCH 1/1] doc: describe u-boot-test-release Heinrich Schuchardt
2025-05-03 21:26 ` Simon Glass
2025-05-05 10:04 ` 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=871pt374qx.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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