linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Howells <dhowells@redhat.com>,
	linux-arch@vger.kernel.org, randy.dunlap@oracle.com
Subject: RE: + expose-range-checking-functions-from-arch-specific.patchadded to -mm tree
Date: Fri, 13 Apr 2007 10:08:03 +1000	[thread overview]
Message-ID: <1176422883.14322.166.camel@localhost.localdomain> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A0157430D@scsmsx411.amr.corp.intel.com>

On Thu, 2007-04-12 at 09:05 -0700, Luck, Tony wrote:
> > Actually, I think it's brilliantly documented.  Defining base as the
> > first valid value and limit as the first invalid value makes it pretty
> > clear, IMHO.
> 
> "first invalid value" is hard to express if the range you
> want to check includes the largest value for the type
> you are using.  Either "limit" needs to be the largest
> allowable value, or you should stick to "base,len".

Hi Tony!

	Sure.  But to be pedantic, that's not a question of documentation: the
documentation made it pretty clear that this expression was not
possible.

Nonetheless, I agree that base+len has merit over start & end.

Cheers,
Rusty.



  reply	other threads:[~2007-04-13  0:08 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 [this message]
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
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=1176422883.14322.166.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).