From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Howells <dhowells@redhat.com>,
akpm@osdl.org, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Keys: Add possessor permissions to keys
Date: Wed, 21 Sep 2005 16:44:04 +0100 [thread overview]
Message-ID: <17063.1127317444@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509210803310.2553@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
> Ok, maybe I'm just strange, but when I see code like
>
> if (is_key_possessed(keyref)) {
>
> I'm inevitably mentally going "Linda Blair! It is spewing pea-soup and
> rotating its head!"
>
> Maybe not the best of naming practices..
Or maybe not the best of mental or film watching practices? :-)
How about if I call it is_key_retained() instead?
Of course, I now prefer the name is_key_possessed() if only to frighten other
kernel developers...
David
next prev parent reply other threads:[~2005-09-21 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5378.1127211442@warthog.cambridge.redhat.com>
2005-09-21 14:48 ` [PATCH] Keys: Add possessor permissions to keys David Howells
2005-09-21 15:05 ` Linus Torvalds
2005-09-21 15:44 ` David Howells [this message]
2005-09-21 17:15 ` Andrew Morton
2005-09-21 17:47 ` Trond Myklebust
2005-09-21 18:36 ` David Howells
2005-09-21 18:29 ` David Howells
2005-09-21 18:45 ` Andrew Morton
2005-09-21 18:56 ` Linus Torvalds
2005-09-22 10:00 ` David Howells
2005-10-03 4:43 ` [Keyrings] " Kyle Moffett
2005-09-21 18:33 ` [PATCH] Keys: Add possessor permissions to keys [try #2] David Howells
2005-09-28 16:03 ` [PATCH] Keys: Add possessor permissions to keys [try #3] David Howells
2005-09-21 19:23 ` [PATCH] Keys: Add possessor permissions to keys 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=17063.1127317444@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@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