From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Sean Anderson <sean.anderson@seco.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [PATCH 2/2] ref-manual: document uboot-sign class and variables
Date: Fri, 12 May 2023 10:13:25 +0200 [thread overview]
Message-ID: <5a6bbc2e-ab65-933d-080b-7fcb38fc4f79@bootlin.com> (raw)
In-Reply-To: <ee686b0e-410f-6ff8-2a10-be6fbb6446cc@seco.com>
Hi Sean,
On 11.05.23 at 20:51, Sean Anderson wrote:
>
>> +- :term:`UBOOT_FIT_GENERATE_KEYS`: allows to generate the keys
>> + if they don't exist yet.
> Remove the "allows to"
Fixed, thanks
>
>> +- :term:`UBOOT_FIT_HASH_ALG`: hash algorithm for the FIT image.
>> +- :term:`UBOOT_FIT_KEY_GENRSA_ARGS`: ``openssl genrsa`` arguments.
>> +- :term:`UBOOT_FIT_KEY_REQ_ARGS`: ``openssl req`` arguments.
>> +- :term:`UBOOT_FIT_SIGN_ALG`: signature algorithm for the FIT image.
>> +- :term:`UBOOT_FIT_SIGN_NUMBITS`: size of the private key for FIT image
>> + signing.
>> +- :term:`UBOOT_FIT_KEY_SIGN_PKCS`: format for the public key certificate
>> + for FIT image signing.
> Maybe "algorithm" instead of "format"? The format stays the same (a
> binary blob), but what's changing is the way the data is interpreted.
Sure, done.
>
>> +- :term:`UBOOT_FITIMAGE_ENABLE`: enables the generation of a U-Boot FIT image.
> enables -> enable
Good catch. Thanks.
All these fixes are now in master-next.
Thanks again
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-05-12 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 16:11 [PATCH 1/2] ref-manual: improve description of kernel-fitimage variables michael.opdenacker
2023-05-11 16:11 ` [PATCH 2/2] ref-manual: document uboot-sign class and variables michael.opdenacker
[not found] ` <ee686b0e-410f-6ff8-2a10-be6fbb6446cc@seco.com>
2023-05-12 8:13 ` Michael Opdenacker [this message]
[not found] ` <d540bdcf-5035-c16f-1118-ef80ab4358e0@seco.com>
2023-05-12 8:05 ` [PATCH 1/2] ref-manual: improve description of kernel-fitimage variables Michael Opdenacker
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=5a6bbc2e-ab65-933d-080b-7fcb38fc4f79@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=sean.anderson@seco.com \
/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