public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: + git-hdrcleanup-vs-git-klibc-on-ia64-2.patch added to -mm tree
Date: Sun, 14 May 2006 21:13:40 +0000	[thread overview]
Message-ID: <je64k8nwcb.fsf@sykes.suse.de> (raw)
In-Reply-To: <1147633985.2551.14.camel@shinybook.infradead.org>

David Woodhouse <dwmw2@infradead.org> writes:

> On Sun, 2006-05-14 at 11:01 -0700, akpm@osdl.org wrote:
>> 
>> diff -puN include/asm-ia64/page.h~git-hdrcleanup-vs-git-klibc-on-ia64-2 include/asm-ia64/page.h
>> --- 25/include/asm-ia64/page.h~git-hdrcleanup-vs-git-klibc-on-ia64-2    Mon May 15 01:48:22 2006
>> +++ 25-akpm/include/asm-ia64/page.h     Mon May 15 01:49:38 2006
>> @@ -36,7 +36,11 @@
>>  #elif defined(CONFIG_IA64_PAGE_SIZE_64KB)
>>  # define PAGE_SHIFT    16
>>  #else
>> +#ifdef __KERNEL__
>>  # error Unsupported page size!
>> +#else
>> +#define PAGE_SHIFT     12
>> +#endif
>>  #endif
>>  
>>  #define PAGE_SIZE              (__IA64_UL_CONST(1) << PAGE_SHIFT)
>
> Hm, same applies here as to the last one. The __KERNEL__ ifdef applies
> to the whole crap around PAGE_SHIFT _and_ PAGE_SIZE, at least. 

Userspace should be using getpagesize() anyway.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2006-05-14 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 19:13 + git-hdrcleanup-vs-git-klibc-on-ia64-2.patch added to -mm tree David Woodhouse
2006-05-14 21:13 ` Andreas Schwab [this message]
2006-05-14 21:17 ` Christoph Hellwig
2006-05-14 21:37 ` David Woodhouse
2006-05-14 22:03 ` H. Peter Anvin
2006-05-14 22:05 ` H. Peter Anvin
2006-05-14 22:11 ` David Woodhouse
2006-05-14 22:34 ` H. Peter Anvin
2006-05-14 22:41 ` David Woodhouse
2006-05-14 23:22 ` H. Peter Anvin
2006-05-14 23:35 ` David Woodhouse

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=je64k8nwcb.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.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