public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: etienne <etienne.basset@numericable.fr>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	LSM <linux-security-module@vger.kernel.org>,
	paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH][SMACK] convert smack_known list to a standard linux list.
Date: Mon, 23 Feb 2009 15:35:33 -0500	[thread overview]
Message-ID: <200902231535.33392.paul.moore@hp.com> (raw)
In-Reply-To: <49A242C6.1000400@numericable.fr>

On Monday 23 February 2009 01:31:34 am etienne wrote:
> Casey Schaufler wrote:
> > etienne wrote:
> >> hello,
> >>
> >> this patch on top of [PATCH][SMACK] convert smack rule list to linux
> >> list V2 converts "smack_known" to a regular linux list. (rcu variant)
> >
> > I'm having some trouble applying this group of patches.
> > I assume that I'm starting at the wrong place. Could you
> > do a single patch to help me avoid confusion?

...

>
> here you are!
> (it is still on top of my 02/20 "[PATCH] SMACK netlabel fixes v2")

If Casey wants to ACK your Smack labeled networking patch from last week I'm 
okay with pulling it into the lblnet-2.6_next tree (it is sorta labeled 
networking related) so you can use it as a base if needed.  It would also get 
the patch into the linux-next tree which is important if you want to target 
2.6.30.

-- 
paul moore
linux @ hp


  reply	other threads:[~2009-02-23 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 21:50 [PATCH][SMACK] convert smack_known list to a standard linux list etienne
2009-02-23  1:51 ` Casey Schaufler
2009-02-23  6:31   ` etienne
2009-02-23 20:35     ` Paul Moore [this message]
2009-02-24  2:56     ` Casey Schaufler

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=200902231535.33392.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=casey@schaufler-ca.com \
    --cc=etienne.basset@numericable.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paulmck@linux.vnet.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