From: Vincent Jardin <vjardin@free.fr>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Sean Anderson <sean.anderson@linux.dev>
Subject: Re: [PATCH v4 3/3] test: py: load: check null_dev_desc_ok dispatch
Date: Wed, 15 Jul 2026 19:09:18 +0200 [thread overview]
Message-ID: <ale-vlEwBRNgIWcD@L30177.local> (raw)
In-Reply-To: <20260715005625.GA4103122@bill-the-cat>
Hi Tom,
> OK, but this fails CI with:
> https://git.u-boot-project.org/u-boot/u-boot/-/jobs/40773
It should be fixed now with the v5. By the way, how can I run/check
my series on u-boot's gitlab runners before sending them ?
I did miss it with my local runs !
Best regards,
Vincent
next prev parent reply other threads:[~2026-07-15 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"<20260601131311.1163914-1-vjardin@free.fr>
2026-07-02 14:42 ` [PATCH v4 0/3] fs: regression-safe load <iface> for null_dev_desc_ok fstypes Vincent Jardin
2026-07-02 14:42 ` [PATCH v4 1/3] fs: dispatch null_dev_desc_ok filesystems before lookup Vincent Jardin
2026-07-02 14:42 ` [PATCH v4 2/3] doc: usage: cmd: load: null-block-device Vincent Jardin
2026-07-02 14:42 ` [PATCH v4 3/3] test: py: load: check null_dev_desc_ok dispatch Vincent Jardin
2026-07-15 0:56 ` Tom Rini
2026-07-15 17:09 ` Vincent Jardin [this message]
2026-07-15 17:23 ` Tom Rini
[not found] <"<20260511115340.675883-1-vjardin@free.fr>
2026-06-01 13:12 ` [PATCH v3 0/3] fs: regression-safe load <iface> for null_dev_desc_ok fstypes Vincent Jardin
2026-06-01 13:12 ` [PATCH v3 1/3] fs: dispatch null_dev_desc_ok filesystems before lookup Vincent Jardin
2026-06-12 18:18 ` Simon Glass
2026-06-01 13:12 ` [PATCH v3 2/3] doc: usage: cmd: load: null-block-device Vincent Jardin
2026-06-12 18:18 ` Simon Glass
2026-06-01 13:12 ` [PATCH v3 3/3] test: py: load: check null_dev_desc_ok dispatch Vincent Jardin
2026-06-12 18:18 ` Simon Glass
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=ale-vlEwBRNgIWcD@L30177.local \
--to=vjardin@free.fr \
--cc=sean.anderson@linux.dev \
--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