From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, Peter.Wahl@oracle.com
Subject: Re: [PATCH] smack: limit privilege by label
Date: Mon, 4 Aug 2008 10:37:28 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0808041035410.18295@us.intercode.com.au> (raw)
In-Reply-To: <4890ED17.6050305@schaufler-ca.com>
On Wed, 30 Jul 2008, Casey Schaufler wrote:
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Reviewed-by: James Morris <jmorris@namei.org>
I also added this to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6.git#next
and #devel.
Holler if you don't want it to go to linux-next this way.
- James
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2008-08-04 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 22:37 [PATCH] smack: limit privilege by label Casey Schaufler
2008-08-04 0:37 ` James Morris [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=Xine.LNX.4.64.0808041035410.18295@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=Peter.Wahl@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--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