From: James Morris <jmorris@namei.org>
To: Paul Moore <pmoore@redhat.com>
Cc: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [GIT PULL] SELinux patches for 3.14
Date: Tue, 7 Jan 2014 02:00:43 +1100 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1401070200000.5247@tundra.namei.org> (raw)
In-Reply-To: <231455217.pFFWomdpV7@sifl>
On Thu, 2 Jan 2014, Paul Moore wrote:
> Hi James,
>
> With 3.13-rc6 out, it looks like it is time to pass along the SELinux pull
> request for 3.14. The tree below includes the patches listed here as well as
> the 3.13-rcX fixes I've sent you previously (I've omitted the 3.13-rcX fixes
> in the list below for the sake of clarity). Of the five new patches here, all
> but Richard's patch are fixes, and minor ones at that.
>
> On a sorta related note, over the past month or two, I've learned that my
> simplistic approach to managing the SELinux tree is just a wee bit too
> simplistic. After the 3.14 merge window closes I'm going to move to a branch
> based approach which should make things a bit easier for everyone (okay,
> mostly me) when it comes to -next and -stable.
>
> Enjoy,
> -Paul
>
> ---
>
> The following changes since commit 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52:
>
> Linux 3.12 (2013-11-03 15:41:51 -0800)
>
> are available in the git repository at:
>
> git://git.infradead.org/users/pcmoore/selinux master
I resync'd my next branch for the TPM pull, and I've now pulled your
request in, too.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2014-01-06 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 23:45 [GIT PULL] SELinux patches for 3.14 Paul Moore
2014-01-03 7:20 ` James Morris
2014-01-03 13:46 ` Paul Moore
2014-01-03 14:03 ` James Morris
2014-01-06 15:00 ` James Morris [this message]
2014-01-06 15:05 ` Paul Moore
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.1401070200000.5247@tundra.namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=pmoore@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.