From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-arch@vger.kernel.org, randy.dunlap@oracle.com
Subject: Re: + expose-range-checking-functions-from-arch-specific.patch added to -mm tree
Date: Wed, 11 Apr 2007 11:31:01 -0700 [thread overview]
Message-ID: <20070411113101.6a444667.akpm@linux-foundation.org> (raw)
In-Reply-To: <400.1176310986@redhat.com>
On Wed, 11 Apr 2007 18:03:06 +0100
David Howells <dhowells@redhat.com> wrote:
> > static inline bool range_over_limit(unsigned long start,
> > unsigned long len,
> > unsigned long limit)
>
> I'm still not sure the name is entirely clear, but it's better. I'd still
> stick the word "check" in there personally, perhaps check_range_limit(), but
> that's just my preference.
If we (crazily) agree that we should/coould/might grow a suite of range-handling
functions then we should stick to the range_foo() namespace for that.
next prev parent reply other threads:[~2007-04-11 18:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 21:27 + expose-range-checking-functions-from-arch-specific.patch added to -mm tree akpm
2007-04-10 10:17 ` David Howells
2007-04-11 2:19 ` Rusty Russell
2007-04-11 2:48 ` Andrew Morton
2007-04-11 10:49 ` David Howells
2007-04-11 18:24 ` Andrew Morton
2007-04-11 23:28 ` Rusty Russell
2007-04-12 16:05 ` + expose-range-checking-functions-from-arch-specific.patchadded " Luck, Tony
2007-04-13 0:08 ` Rusty Russell
2007-04-11 23:41 ` + expose-range-checking-functions-from-arch-specific.patch added " Rusty Russell
2007-04-12 10:47 ` David Howells
2007-04-12 14:51 ` Randy Dunlap
2007-04-12 7:42 ` Geert Uytterhoeven
2007-04-11 13:17 ` Rusty Russell
2007-04-11 17:03 ` David Howells
2007-04-11 18:31 ` Andrew Morton [this message]
2007-04-11 19:17 ` David Howells
2007-04-11 22:52 ` Rusty Russell
2007-04-12 10:49 ` David Howells
2007-04-11 10:47 ` 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=20070411113101.6a444667.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rusty@rustcorp.com.au \
/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.