From: Marek Vasut <marex@denx.de>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Brian Ruley <brian.ruley@gehealthcare.com>,
Paul HENRYS <paul.henrys_ext@softathome.com>,
Rasmus Villemoes <ravi@prevas.dk>,
Tim Harvey <tharvey@gateworks.com>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] binman: Fill in most of the imx8mimage and imx8mcst tests
Date: Fri, 7 Mar 2025 06:42:24 +0100 [thread overview]
Message-ID: <f1e4014e-658b-4a47-af8d-72ef76c1b134@denx.de> (raw)
In-Reply-To: <CAFLszTgF+g2OXz=L=r7rOQcNkk19GfdCrwixG8ZAsR=1rh9Fqw@mail.gmail.com>
On 3/7/25 3:18 AM, Simon Glass wrote:
Hi,
>>>>> One of the main goals of binman is to reduce the work needed to create
>>>>> a working image. If people have to go spelunking around the Internet,
>>>>> build it themselves, etc. that is not good.
>>>> What you are asking me for is not the tool itself, but key material,
>>>> which is generated by these scripts.
>>>
>>> It looks like someone has done this here:
>>>
>>> https://patchwork.ozlabs.org/project/uboot/list/?series=446218
>>>
>>> so I think we are OK now.
>>>
>>> I've applied that series to my tree.
>> OK, does anything need to be done about this patch ?
>
> I'm not sure, but we should apply it anyway as it is a big step forward.
>
> I did send a series to turn on code-coverage checks:
>
> https://patchwork.ozlabs.org/project/uboot/list/?series=446956
So what should we do about this particular patch ?
Should this be applied ? Rebased ? Updated somehow ?
next prev parent reply other threads:[~2025-03-07 5:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 20:36 [PATCH] binman: Fill in most of the imx8mimage and imx8mcst tests Marek Vasut
2025-01-06 14:38 ` Simon Glass
2025-01-06 20:50 ` Marek Vasut
2025-01-07 3:50 ` Simon Glass
2025-01-07 10:39 ` Marek Vasut
2025-01-09 14:10 ` Simon Glass
2025-01-10 11:02 ` Fabio Estevam
2025-02-05 10:19 ` Marek Vasut
2025-02-06 12:42 ` Simon Glass
2025-02-06 20:40 ` Marek Vasut
2025-02-07 0:49 ` Simon Glass
2025-02-08 21:19 ` Marek Vasut
2025-02-15 13:38 ` Simon Glass
2025-02-15 14:55 ` Marek Vasut
2025-03-06 23:30 ` Simon Glass
2025-03-07 0:04 ` Marek Vasut
2025-03-07 2:18 ` Simon Glass
2025-03-07 5:42 ` Marek Vasut [this message]
2025-03-12 0:41 ` Fabio Estevam
2025-03-19 23:54 ` Marek Vasut
2025-03-20 3:40 ` Simon Glass
2025-03-20 4:05 ` Marek Vasut
2025-03-28 11:42 ` Simon Glass
2025-03-28 13:23 ` Fabio Estevam
2025-03-31 14:43 ` Leonard Anderweit
2025-03-31 18:18 ` Fabio Estevam
2025-03-31 18:31 ` Tom Rini
2025-05-05 12:28 ` Fabio Estevam
2025-05-05 14:46 ` Tom Rini
2025-03-30 22:11 ` Marek Vasut
2025-03-31 1: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=f1e4014e-658b-4a47-af8d-72ef76c1b134@denx.de \
--to=marex@denx.de \
--cc=brian.ruley@gehealthcare.com \
--cc=paul.henrys_ext@softathome.com \
--cc=ravi@prevas.dk \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.com \
--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