From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Oren Laadan <orenl@librato.com>
Cc: Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org,
Stephen Smalley <sds@epoch.ncsc.mil>,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 3/3] cr: add selinux support (v4)
Date: Fri, 2 Oct 2009 17:14:56 -0500 [thread overview]
Message-ID: <20091002221456.GD7446@us.ibm.com> (raw)
In-Reply-To: <20091002220556.GB7446@us.ibm.com>
Quoting Serge E. Hallyn (serue@us.ibm.com):
> Quoting Oren Laadan (orenl@librato.com):
> > Please place this (and a few others also in other patches) debug-only
> > changes in a separate patch - it will make my life tremendously easier
> > when merging v18-dev to a nice and clean v19.
>
> Ok, I'll resend those just to containers@ to spare the lsm folks.
Oops, I was thinking this was the patch 1/3. I won't spare the
lsm folks from revised patches 2/3 or 3/3 :)
-serge
next prev parent reply other threads:[~2009-10-02 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 3:49 [PATCH 1/3] cr: add generic LSM c/r support (v4) Serge E. Hallyn
2009-10-02 3:52 ` [PATCH 2/3] cr: add smack support to lsm c/r (v4) Serge E. Hallyn
2009-10-02 3:52 ` [PATCH 3/3] cr: add selinux support (v4) Serge E. Hallyn
2009-10-02 12:59 ` Stephen Smalley
2009-10-02 21:55 ` Serge E. Hallyn
2009-10-02 21:14 ` Oren Laadan
2009-10-02 22:05 ` Serge E. Hallyn
2009-10-02 22:14 ` Serge E. Hallyn [this message]
[not found] ` <20091002034916.GA16871-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-02 3:51 ` [PATCH 1/1] restart: accept the lsm_name field in header and add -k flag Serge E. Hallyn
[not found] ` <20091002035157.GA16920-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-02 21:02 ` Oren Laadan
2009-10-02 20:57 ` [PATCH 1/3] cr: add generic LSM c/r support (v4) Oren Laadan
2009-10-02 22:13 ` Serge E. Hallyn
2009-10-02 22:23 ` Oren Laadan
2009-10-02 22:31 ` Serge E. Hallyn
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=20091002221456.GD7446@us.ibm.com \
--to=serue@us.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-security-module@vger.kernel.org \
--cc=orenl@librato.com \
--cc=sds@epoch.ncsc.mil \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox