From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jes Sorensen <jes@sgi.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
bjorn_helgaas@hp.com, Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@osdl.org>, Robin Holt <holt@sgi.com>,
Dean Nelson <dcn@sgi.com>, Hugh Dickins <hugh@veritas.com>
Subject: Re: [patch] do_no_pfn()
Date: Wed, 20 Sep 2006 08:46:38 -0700 [thread overview]
Message-ID: <20060920084638.900c9a69.rdunlap@xenotime.net> (raw)
In-Reply-To: <yq0u033c84a.fsf@jaguar.mkp.net>
On 20 Sep 2006 03:25:25 -0400 Jes Sorensen wrote:
> include/linux/mm.h | 7 +++++
> mm/memory.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 64 insertions(+), 5 deletions(-)
>
> Index: linux-2.6/include/linux/mm.h
> ===================================================================
> --- linux-2.6.orig/include/linux/mm.h
> +++ linux-2.6/include/linux/mm.h
> @@ -625,6 +626,12 @@ static inline int page_mapped(struct pag
> #define NOPAGE_OOM ((struct page *) (-1))
>
> /*
> + * Error return values for the *_nopfn functions
> + */
> +#define NOPFN_SIGBUS ((unsigned long) -1)
> +#define NOPFN_OOM ((unsigned long) -2)
Is there any difference in the above and
#define NOPFN_SIGBUS -1UL
#define NOPFN_OOM -2UL
?
---
~Randy
next prev parent reply other threads:[~2006-09-20 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 4:33 Arrr! Linux 2.6.18 Linus Torvalds
2006-09-20 4:59 ` Michal Piotrowski
2006-09-20 7:25 ` [patch] do_no_pfn() Jes Sorensen
2006-09-20 15:46 ` Randy.Dunlap [this message]
2006-09-20 16:47 ` Jes Sorensen
2006-09-22 19:49 ` Andrew Morton
2006-09-25 9:31 ` Jes Sorensen
2006-09-22 21:51 ` Arrr! Linux 2.6.18 Judith Lebzelter
2006-09-22 22:08 ` Jeff Garzik
2006-09-22 22:57 ` Dale Farnsworth
2006-09-22 22:58 ` Jeff Garzik
2006-09-29 8:36 ` Mark Lord
2006-09-29 14:49 ` Linus Torvalds
2006-09-29 8:40 ` Mark Lord
2006-09-29 8:44 ` Andrew Morton
2006-09-29 17:52 ` Mark Lord
2006-09-29 19:42 ` Rafael J. Wysocki
2006-09-29 19:58 ` Mark Lord
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=20060920084638.900c9a69.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=bjorn_helgaas@hp.com \
--cc=dcn@sgi.com \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--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
all inboxes | Powered by JetHome®