From: Masahiro Yamada <masahiroy@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Keyrings <keyrings@vger.kernel.org>,
Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: module-signing: Mention default_x509.genkey template
Date: Wed, 24 May 2023 17:47:42 +0900 [thread overview]
Message-ID: <CAK7LNATG=XFvUh-gLNpYyncU47-7mRahze3LBLzQKk=2zSZ02A@mail.gmail.com> (raw)
In-Reply-To: <1955521c-b3eb-d084-71c8-31db72753932@gmail.com>
On Wed, May 24, 2023 at 11:40 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On 5/11/23 23:55, Masahiro Yamada wrote:
> > On Thu, May 11, 2023 at 1:39 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> >>
> >> Commit f3a2ba44e93e2c ("certs: check-in the default x509 config file")
> >> adds default x509 keypair config file template, but forgets to mention
> >> it in kernel module signing documentation.
> >
> > What did it forget?
> >
>
> I mean not mentioning the template.
f3a2ba44e93e2c192a872f2705fe66dbf39708d6
is equivalent to what Makefile previously did.
You could manually copy certs/default_x509.genkey
if you like, but you do not need to.
>
> --
> An old man doll... just what I always wanted! - Clara
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2023-05-24 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 4:38 [PATCH] Documentation: module-signing: Mention default_x509.genkey template Bagas Sanjaya
2023-05-11 16:55 ` Masahiro Yamada
2023-05-12 2:36 ` Bagas Sanjaya
2023-05-24 2:40 ` Bagas Sanjaya
2023-05-24 8:47 ` Masahiro Yamada [this message]
2023-05-24 2:13 ` Jarkko Sakkinen
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='CAK7LNATG=XFvUh-gLNpYyncU47-7mRahze3LBLzQKk=2zSZ02A@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.