public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: serge@hallyn.com
To: Kurt Garloff <garloff@suse.de>, Tony Jones <tonyj@suse.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@osdl.org>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	James Morris <jmorris@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Steve Beattie <smb@wirex.com>,
	Linux LSM list <linux-security-module@wirex.com>
Subject: Re: [PATCH 3/3] Use conditional
Date: Mon, 4 Jul 2005 07:37:21 -0500	[thread overview]
Message-ID: <20050704123721.GA28322@vino.hallyn.com> (raw)
In-Reply-To: <20050704120809.GR11137@tpkurt.garloff.de>

Hey,

Quoting Kurt Garloff (garloff@suse.de):
> Getting rid of dummy entirely would be better, I agree, but someone
> needs to review that this won't break anything.

Unfortunately I think it's way too soon for that.  Even if stacker is
accepted, it is still a module (for now at least) which can be compiled
out.  So we'll need dummy hooks for modules (like seclvl) to use.  I
just don't think it's possible to get rid of that yet.

> So how should we proceed?
> You want to do the dummy removal first, then have stacker merged
> and then what remains of my patches? Or should I start ... ?

I think your patches to make capability the default are the best
place to start.  Doing the same under stacker will be trivial, and
I'll do that in the next set I send out.

thanks,
-serge

  reply	other threads:[~2005-07-04 12:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 15:44 [PATCH 3/3] Use conditional Kurt Garloff
2005-07-03 16:51 ` James Morris
2005-07-03 21:17   ` Kurt Garloff
2005-07-03 19:00 ` Tony Jones
2005-07-04  6:59   ` Kurt Garloff
2005-07-04  7:44     ` Tony Jones
2005-07-04 12:01       ` serge
2005-07-04 12:08         ` Kurt Garloff
2005-07-04 12:37           ` serge [this message]
2005-07-04 13:31             ` Kurt Garloff

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=20050704123721.GA28322@vino.hallyn.com \
    --to=serge@hallyn.com \
    --cc=chrisw@osdl.org \
    --cc=garloff@suse.de \
    --cc=gregkh@suse.de \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=smb@wirex.com \
    --cc=tonyj@suse.de \
    /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