From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: 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 09:22:03 +1000 [thread overview]
Message-ID: <20140718092203.3bab9fba@canb.auug.org.au> (raw)
In-Reply-To: <23717.1405636445@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Hi David,
On Thu, 17 Jul 2014 23:34:05 +0100 David Howells <dhowells@redhat.com> wrote:
>
> I have a number of sets of patches for you to pull. I've git-merged them
> together into a single branch (keys-next) as there are some conflicts and
> tagged the end.
>
> The component subsets are:
>
> (1) Tag keys-preparse-1-20140707
>
> A set of patches that mostly convert extant key types to perform
> preparsing to make it possible to determine the amount of quota in
> advance.
>
> I haven't fixed the encrypted and trusted keys as yet as they incorrectly
> use the ->update() op, but I'd like to get the changes I have done out
> the door.
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 ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-17 23:22 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 [this message]
2014-07-18 19:07 ` David Howells
-- 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=20140718092203.3bab9fba@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=d.kasatkin@samsung.com \
--cc=dhowells@redhat.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=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