From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, dwalsh@redhat.com, vgoyal@redhat.com,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [GIT PULL] keys: Namespacing
Date: Wed, 01 May 2019 18:18:29 +0100 [thread overview]
Message-ID: <22943.1556731109@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.21.1905020306290.14696@namei.org>
James Morris <jmorris@namei.org> wrote:
> > Can you pull this set of patches into the security tree and pass them along
> > to Linus in the next merge window? The primary thrust is to add
> > namespacing to keyrings.
>
> Not for this merge window, it's too close. Something like this would need
> to be in -rc2 or so.
Okay.
David
prev parent reply other threads:[~2019-05-01 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 22:39 [GIT PULL] keys: Namespacing David Howells
2019-05-01 17:07 ` James Morris
2019-05-01 17:18 ` 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=22943.1556731109@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dwalsh@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).