public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Chris Wright <chrisw@osdl.org>
Cc: David Howells <dhowells@redhat.com>,
	torvalds@osdl.org, akpm@osdl.org, keyrings@linux-nfs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Keyrings] [PATCH] Keys: Add LSM hooks for key management [try #2]
Date: Sat, 08 Oct 2005 00:38:54 +0100	[thread overview]
Message-ID: <12790.1128728334@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20051007233547.GH5856@shell0.pdx.osdl.net>

Chris Wright <chrisw@osdl.org> wrote:

> I thought that too at first, which is why I flagged it at first.  But I
> think it's actually not a real problem, because isn't that !CONFIG_KEYS?
> So, I think it's just cosmetic.

It is a problem; at least I found it to be one. And no it isn't !CONFIG_KEYS.

David

  reply	other threads:[~2005-10-07 23:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 14:07 [PATCH] Keys: Split key permissions checking into a .c file David Howells
2005-10-07 15:41 ` [PATCH] Keys: Possessor permissions should be additive David Howells
2005-10-07 15:57   ` [PATCH] Keys: Add LSM hooks for key management [try #2] David Howells
2005-10-07 16:08     ` [PATCH] Keys: Remove key duplication David Howells
2005-10-07 22:04     ` [Keyrings] [PATCH] Keys: Add LSM hooks for key management [try #2] Chris Wright
2005-10-07 23:34       ` David Howells
2005-10-07 23:35         ` Chris Wright
2005-10-07 23:38           ` David Howells [this message]
2005-10-07 23:45             ` David Howells
2005-10-07 23:46               ` Chris Wright
2005-10-07 23:46             ` Chris Wright
2005-10-08  6:51   ` [PATCH] Keys: Add LSM hooks for key management [try #3] Chris Wright
2005-11-01 14:16 ` [PATCH] Keys: Remove incorrect and obsolete '!' operators David Howells

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=12790.1128728334@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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