From: James Morris <jmorris@namei.org>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [GIT] Security subsystem updates for 3.13
Date: Tue, 19 Nov 2013 10:30:19 +1100 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1311191029050.20131@tundra.namei.org> (raw)
In-Reply-To: <CA+5PVA7C-SSg5TyQ14kUN2SbLi-=bk6isi05xgtR5j8MC7-Uhg@mail.gmail.com>
On Mon, 18 Nov 2013, Josh Boyer wrote:
> On Wed, Nov 6, 2013 at 7:51 PM, James Morris <jmorris@namei.org> wrote:
> > In this patchset, we finally get an SELinux update, with Paul Moore taking
> > over as maintainer of that code.
> >
> > Also a significant update for the Keys subsystem, as well as maintenance
> > updates to Smack, IMA, TPM, and Apparmor.
> >
> > Please pull.
> >
> > The following changes since commit be408cd3e1fef73e9408b196a79b9934697fe3b1:
> >
> > Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-11-04 06:40:55 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git for-linus
>
> Unless I'm missing something, I don't think this has landed in Linus'
> tree yet. Linus, did this pull request get NAKed or fall through the
> cracks?
I think Linus is on vacation and merging only sporadically at the moment.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2013-11-18 23:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 0:51 James Morris
2013-11-18 15:31 ` Josh Boyer
2013-11-18 23:30 ` James Morris [this message]
2013-11-18 23:54 ` Linus Torvalds
2013-11-19 5:38 ` James Morris
2013-11-19 12:20 ` James Morris
2013-11-22 4:22 ` Linus Torvalds
2013-11-22 9:36 ` James Morris
2013-11-22 14:01 ` Josh Boyer
2013-11-22 20:25 ` David Howells
2013-11-24 3:33 ` Linus Torvalds
2013-11-25 2:15 ` James Morris
2013-11-19 14:46 ` David Howells
2013-11-23 6:05 George Spelvin
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=alpine.LRH.2.02.1311191029050.20131@tundra.namei.org \
--to=jmorris@namei.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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®