public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Fabio Estevam <festevam@gmail.com>,
	Brian Ruley <brian.ruley@gehealthcare.com>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	ian.ray@gehealthcare.com, Marek Vasut <marex@denx.de>,
	u-boot@lists.denx.de
Subject: Re: [PATCH] binman: add fast authentication method for i.MX8M signing
Date: Sun, 29 Sep 2024 18:46:23 -0600	[thread overview]
Message-ID: <20240930004623.GA5579@bill-the-cat> (raw)
In-Reply-To: <CAFLszTiUQBJvaU_bhUYdsujo-oeeT8RCDguu+pYQ9YEppqqALg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On Sun, Sep 29, 2024 at 04:49:17PM -0600, Simon Glass wrote:
> Hi Fabio,
> 
> On Sun, 29 Sept 2024 at 14:53, Fabio Estevam <festevam@gmail.com> wrote:
> >
> > Hi Simon, Marek, and Tom,
> >
> > On Fri, Sep 27, 2024 at 5:47 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > > > Please can you coordinate with Marek as we need to sort out the test
> > > > coverage for this etype, before adding more functionality. I did a
> > > > starting point, now in -next, which should help.
> > >
> > > Well, when someone has both time and understanding of the tools and the
> > > frameworks, we can expand the automatic tests while still having
> > > functional testing as people use the feature.
> >
> > Do you think this patch should be applied as is? Could the tests be
> > handled later?
> >
> > Please let me know.
> 
> Who is going to handle the tests later and when?

Someone, once how to write and run the tests is documented. That's a
big hurdle this private thread has shown, to me at least.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-09-30  0:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 12:42 [PATCH] binman: add fast authentication method for i.MX8M signing Brian Ruley
2024-09-27 16:50 ` Simon Glass
2024-09-27 20:40   ` Tom Rini
2024-09-29 20:53     ` Fabio Estevam
2024-09-29 22:49       ` Simon Glass
2024-09-30  0:46         ` Tom Rini [this message]
2024-09-30 11:28           ` Brian Ruley
2024-09-30 14:10             ` Simon Glass
2024-09-30 14:47               ` Brian Ruley
2024-09-30 15:55                 ` Simon Glass
2024-09-30 10:21 ` [PATCH v2] " Brian Ruley
2024-09-30 16:10   ` [PATCH v3 1/2] binman: cosmetic: code formatting fixes Brian Ruley
2024-09-30 16:10     ` [PATCH v3 2/2] binman: add fast authentication method for i.MX8M signing Brian Ruley
2024-09-30 18:52       ` Simon Glass
2024-09-30 18:52     ` [PATCH v3 1/2] binman: cosmetic: code formatting fixes Simon Glass
2024-10-02  6:41       ` Brian Ruley
2024-10-02 22:55         ` Simon Glass
2024-10-07 12:33           ` Brian Ruley
2024-10-09  1:57             ` Simon Glass
2024-10-01 13:58     ` [PATCH v4 1/2] binman: cosmetic: refactor `nxp_imx8mcst' etype code Brian Ruley
2024-10-01 13:58       ` [PATCH v4 2/2] binman: add fast authentication method for i.MX8M signing Brian Ruley
2024-10-08 14:10         ` Fabio Estevam
2024-10-09  1:57         ` Simon Glass
2024-10-13 20:21           ` Fabio Estevam

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=20240930004623.GA5579@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=brian.ruley@gehealthcare.com \
    --cc=festevam@gmail.com \
    --cc=ian.ray@gehealthcare.com \
    --cc=marex@denx.de \
    --cc=sjg@chromium.org \
    --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