From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] KEYS: Miscellaneous fixes
Date: Tue, 16 Sep 2014 10:07:56 +0100 [thread overview]
Message-ID: <18406.1410858476@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1409161215030.10183@namei.org>
James Morris <jmorris@namei.org> wrote:
> Can you split your pull requests into different branches -- one which is
> for current upstream, and one which is for next?
I had already done that. But if you really want, I can punt #3 and #4 over to
linux-next.
David
prev parent reply other threads:[~2014-09-16 9:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 21:21 David Howells
2014-09-10 21:22 ` [PATCH 1/6] KEYS: Fix termination condition in assoc array garbage collection David Howells
2014-09-10 21:22 ` [PATCH 2/6] KEYS: Reinstate EPERM for a key type name beginning with a '.' David Howells
2014-09-10 23:36 ` Mimi Zohar
2014-09-11 11:43 ` Mimi Zohar
2014-09-11 12:09 ` David Howells
2014-09-11 12:27 ` Dmitry Kasatkin
2014-09-11 12:28 ` Dmitry Kasatkin
2014-09-11 13:46 ` Mimi Zohar
2014-09-11 21:26 ` David Howells
2014-09-10 21:22 ` [PATCH 3/6] KEYS: Fix missing statics David Howells
2014-09-10 21:22 ` [PATCH 4/6] PKCS#7: Add a missing static David Howells
2014-09-10 21:22 ` [PATCH 5/6] PKCS#7: Provide a single place to do signed info block freeing David Howells
2014-09-10 21:22 ` [PATCH 6/6] PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs David Howells
2014-09-15 13:04 ` [PATCH 0/6] KEYS: Miscellaneous fixes David Howells
2014-09-16 2:15 ` James Morris
2014-09-16 9:07 ` David Howells [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=18406.1410858476@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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
all inboxes | Powered by JetHome®