From: Casey Schaufler <casey@schaufler-ca.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org,
SELinux <selinux@tycho.nsa.gov>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [RFC PATCH 2/2] cr: debug security_checkpoint_header and security_may_restart
Date: Wed, 09 Sep 2009 07:52:40 -0700 [thread overview]
Message-ID: <4AA7C138.6000205@schaufler-ca.com> (raw)
In-Reply-To: <20090909143542.GA23322@us.ibm.com>
Serge E. Hallyn wrote:
> Quoting Casey Schaufler (casey@schaufler-ca.com):
>
>> Serge E. Hallyn wrote:
>>
>>> Quoting Casey Schaufler (casey@schaufler-ca.com):
>>> Sorry, the c/r tree is at:
>>>
>>> git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git
>>>
>>>
>> The four patches from 08/28 (2-5) and the two from 09/03
>> are not happy applying to this tree. Am I missing a patch?
>>
>>
>
> There was this patch which was 1/5
> https://lists.linux-foundation.org/pipermail/containers/2009-August/020212.html
>
> But there have also been some changes since that posting to the
> git tree. You could rewind the git tree to the state it was in
> on aug 28, but I'll need to forward-port my patches anyway, so
> let me do that this afternoon and resend the patchset.
>
>
I figured it was something like that. Thank you.
next prev parent reply other threads:[~2009-09-09 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 22:28 [RFC PATCH 1/2] cr: lsm: provide hooks for an LSM to track policy changes Serge E. Hallyn
2009-09-03 22:28 ` [RFC PATCH 2/2] cr: debug security_checkpoint_header and security_may_restart Serge E. Hallyn
2009-09-04 5:20 ` Casey Schaufler
2009-09-04 13:46 ` Serge E. Hallyn
2009-09-07 18:31 ` Casey Schaufler
2009-09-08 4:12 ` Serge E. Hallyn
2009-09-09 4:43 ` Casey Schaufler
2009-09-09 14:35 ` Serge E. Hallyn
2009-09-09 14:52 ` Casey Schaufler [this message]
2009-09-09 19:46 ` 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=4AA7C138.6000205@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=containers@lists.osdl.org \
--cc=linux-security-module@vger.kernel.org \
--cc=orenl@cs.columbia.edu \
--cc=selinux@tycho.nsa.gov \
--cc=serue@us.ibm.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