From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, James Morris <jmorris@namei.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
mimi.e.zohar@gmail.com, Dmitry Kasatkin <d.kasatkin@samsung.com>,
vgoyal@redhat.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Keyrings and asymmetric keys patches for 3.17
Date: Fri, 18 Jul 2014 20:07:47 +0100 [thread overview]
Message-ID: <21814.1405710467@warthog.procyon.org.uk> (raw)
In-Reply-To: <20140718092203.3bab9fba@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I hate to be a pest, but this whole branch has only your signed off by
> and no indication that any of it has been reviewed/tested by anyone
> else ...
Okay, I've got at least one review for most of the patches. I'll try and get
some more, but it probably won't be till next week.
Anyway, I've updated the keys-preparse-1 branch and tagged it anew with
keys-preparse-1-20140718. There was a spelling fix in the docs and the
patches have been rebased on the updated security/next.
I've also rebuilt the keys-next branch, basing it on the updated
security/next, and tagged it with keys-next-20140718.
warthog>git diff keys-next-20140717 keys-next-20140718 | diffstat
keys.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
David
next prev parent reply other threads:[~2014-07-18 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 22:34 [GIT PULL] Keyrings and asymmetric keys patches for 3.17 David Howells
2014-07-17 23:22 ` Stephen Rothwell
2014-07-18 19:07 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-22 21:07 David Howells
2014-07-24 11:37 ` James Morris
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=21814.1405710467@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=d.kasatkin@samsung.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mimi.e.zohar@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.vnet.ibm.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