From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <rusty@rustcorp.com.au>
Cc: <torvalds@transmeta.com>, <akpm@zip.com.au>, <rth@twiddle.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] __optional and __keep
Date: Wed, 14 May 2003 22:54:27 -0700 (PDT) [thread overview]
Message-ID: <2418.4.64.196.31.1052978067.squirrel@www.osdl.org> (raw)
In-Reply-To: <20030515021624.B814B2C017@lists.samba.org>
> Hi all!
>
> Does anyone else find __attribute_used__ confusing, or is it just me? In the
> tradition of likely() and unlikely(), I think __optional and __keep are
> clearer.
>
> Thoughts?
> Rusty.
> --
Yes, I thought that we had already hashed thru this one time.
I'm fine with the current naming.
~Randy
prev parent reply other threads:[~2003-05-15 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 2:09 Rusty Russell
2003-05-15 5:54 ` Randy.Dunlap [this message]
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=2418.4.64.196.31.1052978067.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®