From: Michael Olbrich <mol@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: dev_code_signing: mention where to select the signing provider
Date: Fri, 05 Mar 2021 08:26:13 +0100 [thread overview]
Message-ID: <E1lI4qj-000ALk-1a@dude03.red.stw.pengutronix.de> (raw)
In-Reply-To: <20210228234809.5294-1-rhi@pengutronix.de>
Thanks, applied as dd524817b207b8de40fede2ac183e336030d995b.
Michael
[sent from post-receive hook]
On Fri, 05 Mar 2021 08:26:13 +0100, Roland Hieber <rhi@pengutronix.de> wrote:
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20210228234809.5294-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/dev_code_signing.rst b/doc/dev_code_signing.rst
> index d47002e8c380..56ac0e3b3217 100644
> --- a/doc/dev_code_signing.rst
> +++ b/doc/dev_code_signing.rst
> @@ -49,6 +49,7 @@ material in case SoftHSM is used.
>
> When ``PTXCONF_CODE_SIGNING`` is enabled exactly one code signing provider is
> active during each invocation of PTXdist.
> +The active provider can be selected in the ``platformconfig`` menu.
>
> PTXdist comes equipped with a development code signing provider "devel"
> implemented via the package ``host-ptx-code-signing-dev``.
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-03-05 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 23:48 [ptxdist] [PATCH 1/2] " Roland Hieber
2021-02-28 23:48 ` [ptxdist] [PATCH 2/2] rauc: be more verbose why the check for legacy keyring fails Roland Hieber
2021-03-05 7:26 ` [ptxdist] [APPLIED] " Michael Olbrich
2021-03-05 7:26 ` Michael Olbrich [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=E1lI4qj-000ALk-1a@dude03.red.stw.pengutronix.de \
--to=mol@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.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