From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 0/5] Add code-signing-provider template, add code signing docs
Date: Tue, 9 Jun 2020 17:04:03 +0200 [thread overview]
Message-ID: <20200609150403.GA1864869@lenoch> (raw)
In-Reply-To: <20200608101703.tehl7qrrqxlmron2@pengutronix.de>
On Mon, Jun 08, 2020 at 12:17:03PM +0200, Roland Hieber wrote:
> On Mon, Jun 08, 2020 at 10:53:00AM +0200, Bastian Krause wrote:
> > The code signing infrastructure is available since 2019 in PTXdist. Now
> > it's time to document it, especially since RAUC also uses it.
> > Unfortunately this did not make it into ptxdist-2020.06.0.
> >
> > To make things easier introduce a code-signing-provider template.
> >
> > Bastian Krause (5):
> > package templates: add code-signing-provider template
> > doc: dev_manual: split up into multiple files
> > doc: move code signing docs from scripts/ into doc/
> > doc: dev_code_signing: rework and extend code signing section
> > doc: introduce ref_code_signing_helpers
>
> For the whole series:
>
> Reviewed-by: Roland Hieber <rhi@pengutronix.de>
...and as I successfully migrated my BSP to code-signing-provider using
this documentation (and template):
Tested-by: Ladislav Michl <ladis@linux-mips.org>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-06-09 15:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 8:53 Bastian Krause
2020-06-08 8:53 ` [ptxdist] [PATCH 1/5] package templates: add code-signing-provider template Bastian Krause
2020-06-12 9:18 ` Michael Olbrich
2020-06-12 9:54 ` Michael Olbrich
2020-06-12 10:05 ` Michael Olbrich
2020-06-12 11:05 ` Bastian Krause
2020-06-17 14:45 ` Bastian Krause
2020-06-16 13:56 ` Bastian Krause
2020-06-16 15:00 ` Michael Olbrich
2020-06-08 8:53 ` [ptxdist] [PATCH 2/5] doc: dev_manual: split up into multiple files Bastian Krause
2020-06-08 8:53 ` [ptxdist] [PATCH 3/5] doc: move code signing docs from scripts/ into doc/ Bastian Krause
2020-06-08 8:53 ` [ptxdist] [PATCH 4/5] doc: dev_code_signing: rework and extend code signing section Bastian Krause
2020-06-08 10:16 ` Roland Hieber
2020-06-12 8:55 ` Bastian Krause
2020-06-08 8:53 ` [ptxdist] [PATCH 5/5] doc: introduce ref_code_signing_helpers Bastian Krause
2020-06-12 9:28 ` Michael Olbrich
2020-06-12 9:49 ` Michael Olbrich
2020-06-08 10:17 ` [ptxdist] [PATCH 0/5] Add code-signing-provider template, add code signing docs Roland Hieber
2020-06-09 15:04 ` Ladislav Michl [this message]
2020-06-12 10:04 ` Michael Olbrich
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=20200609150403.GA1864869@lenoch \
--to=ladis@linux-mips.org \
--cc=bst@pengutronix.de \
--cc=ptxdist@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