From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: [PATCH 5/6] AVR32: Use linux/pfn.h
Date: Mon, 31 Jul 2006 15:55:59 +0200 [thread overview]
Message-ID: <11543541603922-git-send-email-hskinnemoen@atmel.com> (raw)
In-Reply-To: <11543541601135-git-send-email-hskinnemoen@atmel.com>
As pointed out by Dave Hansen, we should really use linux/pfn.h
instead of our own PFN_UP/PFN_DOWN/PFN_PHYS definitions.
Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
---
arch/avr32/mm/init.c | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/arch/avr32/mm/init.c b/arch/avr32/mm/init.c
index 7bbbd7e..e4b6707 100644
--- a/arch/avr32/mm/init.c
+++ b/arch/avr32/mm/init.c
@@ -14,6 +14,7 @@ #include <linux/initrd.h>
#include <linux/mmzone.h>
#include <linux/bootmem.h>
#include <linux/pagemap.h>
+#include <linux/pfn.h>
#include <linux/nodemask.h>
#include <asm/page.h>
@@ -90,10 +91,6 @@ static void __init print_memory_map(cons
}
}
-#define PFN_UP(x) (((x) + PAGE_SIZE - 1) >> PAGE_SHIFT)
-#define PFN_DOWN(x) ((x) >> PAGE_SHIFT)
-#define PFN_PHYS(x) ((x) << PAGE_SHIFT)
-
#define MAX_LOWMEM HIGHMEM_START
#define MAX_LOWMEM_PFN PFN_DOWN(MAX_LOWMEM)
--
1.4.0
next prev parent reply other threads:[~2006-07-31 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 13:55 [PATCH 1/6] AVR32: Use auto.conf instead of MARKER Haavard Skinnemoen
2006-07-31 13:55 ` [PATCH 2/6] AVR32: Don't assume anything about MAX_NR_ZONES Haavard Skinnemoen
2006-07-31 13:55 ` [PATCH 3/6] AVR32: Add nsproxy definition Haavard Skinnemoen
2006-07-31 13:55 ` [PATCH 4/6] AVR32: Add I/O port access primitives Haavard Skinnemoen
2006-07-31 13:55 ` Haavard Skinnemoen [this message]
2006-07-31 13:56 ` [PATCH 6/6] AVR32: Kill CONFIG_DISCONTIGMEM support completely Haavard Skinnemoen
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=11543541603922-git-send-email-hskinnemoen@atmel.com \
--to=hskinnemoen@atmel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®