From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 2/3] test: vboot: add tests for multiple required keys
Date: Tue, 13 Oct 2020 10:06:43 -0400 [thread overview]
Message-ID: <20201013140643.GI14816@bill-the-cat> (raw)
In-Reply-To: <984588c7a40a2217d108f304559645d9767b3589.1597643014.git.thiruan@linux.microsoft.com>
On Sun, Aug 16, 2020 at 11:01:10PM -0700, Thirupathaiah Annapureddy wrote:
> This patch adds vboot tests to verify the support for multiple
> required keys using new required-mode DTB policy.
>
> This patch also fixes existing test where dev
> key is assumed to be marked as not required, although
> it is marked as required.
>
> Note that this patch re-added sign_fit_norequire().
> sign_fit_norequire() was removed as part of the following:
> commit b008677daf2a ("test: vboot: Fix pylint errors").
> This patch leverages sign_fit_norequire() to fix the
> existing bug.
>
> Signed-off-by: Thirupathaiah Annapureddy <thiruan@linux.microsoft.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201013/280fd7e2/attachment.sig>
next prev parent reply other threads:[~2020-10-13 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 6:01 [PATCH v3 0/3] Add support for multiple required keys Thirupathaiah Annapureddy
2020-08-17 6:01 ` [PATCH v3 1/3] vboot: add DTB policy for supporting multiple required conf keys Thirupathaiah Annapureddy
2020-10-13 14:06 ` Tom Rini
2020-08-17 6:01 ` [PATCH v3 2/3] test: vboot: add tests for multiple required keys Thirupathaiah Annapureddy
2020-10-13 14:06 ` Tom Rini [this message]
2020-08-17 6:01 ` [PATCH v3 3/3] doc: verified-boot: add required-mode information Thirupathaiah Annapureddy
2020-10-13 14: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=20201013140643.GI14816@bill-the-cat \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.