All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Greg KH <greg@kroah.com>
Cc: linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] LSM fix for stupid "empty" functions - take 2
Date: Wed, 4 Dec 2002 15:44:44 -0800	[thread overview]
Message-ID: <20021204154444.A575@figure1.int.wirex.com> (raw)
In-Reply-To: <20021204230050.GB29519@kroah.com>; from greg@kroah.com on Wed, Dec 04, 2002 at 03:00:50PM -0800

* Greg KH (greg@kroah.com) wrote:
> On Wed, Dec 04, 2002 at 12:14:38AM -0800, Chris Wright wrote:
> > 
> > Also, I think the fixup should go directly in verify, since they are
> > always called together.  Otherwise, this looks good.  Thanks, it's been
> > sorely needed.
> 
> Thanks for the changes, I'll use your version of this :)

alright, thanks.
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2002-12-04 23:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01  8:30 [RFC] LSM fix for stupid "empty" functions Greg KH
2002-12-01  8:17 ` Crispin Cowan
2002-12-01 17:49   ` Greg KH
2002-12-01 16:59 ` Olaf Dietsche
2002-12-01 18:12   ` Greg KH
2002-12-01 17:21     ` Christoph Hellwig
2002-12-01 18:26       ` Greg KH
2002-12-03  2:37         ` Dragan Stancevic
2002-12-03 16:01           ` Greg KH
2002-12-03 15:14             ` Dragan Stancevic
2002-12-01 17:46     ` James Morris
2002-12-01 18:46       ` Olaf Dietsche
2002-12-01 20:05         ` Greg KH
2002-12-01 19:25       ` Greg KH
2002-12-02  2:00         ` James Morris
2002-12-02  6:57           ` Greg KH
2002-12-03  8:04             ` James Morris
2002-12-04  0:13 ` [RFC] LSM fix for stupid "empty" functions - take 2 Greg KH
2002-12-04  8:14   ` Chris Wright
2002-12-04 23:00     ` Greg KH
2002-12-04 23:44       ` Chris Wright [this message]
2002-12-05  0:09   ` James Morris

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=20021204154444.A575@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.