From: Tom Rini <trini@konsulko.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Simon Glass <sjg@chromium.org>,
Ivan Mikhaylov <ivan.mikhaylov@siemens.com>
Subject: Re: [resent][PATCH 3/3] mkimage: Allow to specify the signature algorithm on the command line
Date: Mon, 24 Jan 2022 11:53:27 -0500 [thread overview]
Message-ID: <20220124165327.GA7515@bill-the-cat> (raw)
In-Reply-To: <7e2e0ff69bd1c756669955ff29ca9ed068c2d2ee.1642152079.git.jan.kiszka@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Fri, Jan 14, 2022 at 10:21:19AM +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> This permits to prepare FIT image description that do not hard-code the
> final choice of the signature algorithm, possibly requiring the user to
> patch the sources.
>
> When -o <algo> is specified, this information is used in favor of the
> 'algo' property in the signature node. Furthermore, that property is set
> accordingly when writing the image.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-01-24 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 9:21 [resent][PATCH 0/3] mkimage: allow to specify signing algorithm Jan Kiszka
2022-01-14 9:21 ` [resent][PATCH 1/3] image-fit: Make string of algo parameter constant Jan Kiszka
2022-01-21 15:20 ` Simon Glass
2022-01-24 16:53 ` Tom Rini
2022-01-14 9:21 ` [resent][PATCH 2/3] mkimage: Drop unused OPT_STRING constant Jan Kiszka
2022-01-21 15:20 ` Simon Glass
2022-01-24 16:53 ` Tom Rini
2022-01-14 9:21 ` [resent][PATCH 3/3] mkimage: Allow to specify the signature algorithm on the command line Jan Kiszka
2022-01-21 15:20 ` Simon Glass
2022-01-24 16:53 ` Tom Rini [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=20220124165327.GA7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=ivan.mikhaylov@siemens.com \
--cc=jan.kiszka@siemens.com \
--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