public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
	James Solner <solner@alcatel-lucent.com>,
	David Howells <dhowells@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Adding Documentation/module-signing.txt file
Date: Mon, 11 Nov 2013 02:14:06 -0600	[thread overview]
Message-ID: <1384157646.1974.265@driftwood> (raw)
In-Reply-To: <5279B82E.7000600@infradead.org> (from rdunlap@infradead.org on Tue Nov  5 21:31:58 2013)

On 11/05/2013 09:31:58 PM, Randy Dunlap wrote:
> On 11/05/13 14:54, Rob Landley wrote:
> > On 10/24/2013 07:08:33 PM, Josh Boyer wrote:
> >> On Thu, Oct 24, 2013 at 6:35 PM, James Solner  
> <solner@alcatel-lucent.com> wrote:
> >> > This patch adds the Documentation/module-signing.txt file that is
> >> > missing. There is a link to Documentation/module-signing.txt file
> >> > in init/Kconfig that references this file.
> >> >
> >> > Signed-off-by: James Solner <solner@alcatel-lucent.com>
> >>
> >> Nak.  Please see below.
...
> There was a new version posted earlier today:
> http://marc.info/?l=linux-kernel&m=138369435917393&w=2
> 
> 
> It still needs to be cleaned up IMO.

Is there any place other than the top level Documentation directory to  
put it? (Start a modules subdirectory, maybe?)

Rob

      reply	other threads:[~2013-11-11  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 22:35 [PATCH] Adding Documentation/module-signing.txt file James Solner
2013-10-25  0:08 ` Josh Boyer
2013-11-05 22:54   ` Rob Landley
2013-11-06  3:31     ` Randy Dunlap
2013-11-11  8:14       ` Rob Landley [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=1384157646.1974.265@driftwood \
    --to=rob@landley.net \
    --cc=dhowells@redhat.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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