From: Randy Dunlap <rdunlap@infradead.org>
To: James Solner <solner@alcatel-lucent.com>,
dhowells@redhat.com, rusty@rustcorp.com.au,
jwboyer@fedoraproject.org
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] Add Documentation/module-signing.txt file
Date: Wed, 06 Nov 2013 12:32:08 -0800 [thread overview]
Message-ID: <527AA748.7070008@infradead.org> (raw)
In-Reply-To: <2816992.xgHeIJfXWn@cmlinux10.ih.lucent.com>
On 11/06/13 10:53, James Solner wrote:
> This patch adds the Documentation/module-signing.txt file that is
> currently missing from the Documentation directory. The init/Kconfig
> file references the Documentation/module-signing.txt file to explain
> how kernel module signing works. This patch supplies this documentation.
>
> The initial version of this patch provided old documentation
> that was a mixture of the old RHEL style GPG signing.
> Version 1 updated the documentation to described the current
> implementation using x509 certificate signing.
> Version 2, fixes grammar/spelling mistakes and removes
> trailing whitespaces. Version 3, fixes grammar/spelling mistakes.
>
> Signed-off-by: James Solner <solner@alcatel-lucent.com>
>
Looks good to me. I'll let David, Josh, Rusty, et al, comment
on the real content.
Thanks.
> ---
> Documentation/module-signing.txt | 115 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 115 insertions(+)
> create mode 100644 Documentation/module-signing.txt
--
~Randy
next prev parent reply other threads:[~2013-11-06 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 18:53 [PATCH v3] Add Documentation/module-signing.txt file James Solner
2013-11-06 20:32 ` Randy Dunlap [this message]
2013-11-07 3:02 ` Rusty Russell
2013-11-08 17:49 ` David Howells
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=527AA748.7070008@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=solner@alcatel-lucent.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;
as well as URLs for NNTP newsgroup(s).