From: Rusty Russell <rusty@rustcorp.com.au>
To: David Howells <dhowells@redhat.com>,
James Solner <solner@alcatel-lucent.com>
Cc: dhowells@redhat.com, Josh Boyer <jwboyer@fedoraproject.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] Add Documentation/module-signing.txt file
Date: Wed, 20 Nov 2013 12:56:33 +1030 [thread overview]
Message-ID: <878uwjdd0m.fsf@rustcorp.com.au> (raw)
In-Reply-To: <29909.1384452051@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> writes:
> James Solner <solner@alcatel-lucent.com> 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.
>>
>> Version 4: Include updates from David Howells and fixes for
>> spelling mistakes.
>>
>> Signed-off-by: James Solner <solner@alcatel-lucent.com>
>
> Signed-off-by: David Howells <dhowells@redhat.com>
? I changed this to an Acked-by...
Cheers,
Rusty.
next prev parent reply other threads:[~2013-11-20 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 16:36 [PATCH v4] Add Documentation/module-signing.txt file James Solner
2013-11-14 18:00 ` David Howells
2013-11-20 2:26 ` Rusty Russell [this message]
2013-11-20 11:09 ` David Howells
2013-11-27 16:03 ` Rob Landley
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=878uwjdd0m.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dhowells@redhat.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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