public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Wu Fengguang <fengguang.wu@intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	tglx@linutronix.de, fengguang.wu@intel.com
Subject: [tip:x86/mm] Move page_is_ram() declaration to mm.h
Date: Tue, 2 Feb 2010 01:01:05 GMT	[thread overview]
Message-ID: <tip-53df8fdc15fb646b0219e43c989c2cdab1ab100c@git.kernel.org> (raw)
In-Reply-To: <20100127030639.GD8132@localhost>

Commit-ID:  53df8fdc15fb646b0219e43c989c2cdab1ab100c
Gitweb:     http://git.kernel.org/tip/53df8fdc15fb646b0219e43c989c2cdab1ab100c
Author:     Wu Fengguang <fengguang.wu@intel.com>
AuthorDate: Wed, 27 Jan 2010 11:06:39 +0800
Committer:  H. Peter Anvin <hpa@zytor.com>
CommitDate: Mon, 1 Feb 2010 16:58:17 -0800

Move page_is_ram() declaration to mm.h

Move page_is_ram() declaration to mm.h, it makes no sense in <linux/ioport.h>.

Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
LKML-Reference: <20100127030639.GD8132@localhost>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
 include/linux/ioport.h |    2 --
 include/linux/mm.h     |    2 ++
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 11ef795..83aa812 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -188,7 +188,5 @@ extern int
 walk_system_ram_range(unsigned long start_pfn, unsigned long nr_pages,
 		void *arg, int (*func)(unsigned long, unsigned long, void *));
 
-extern int page_is_ram(unsigned long pfn);
-
 #endif /* __ASSEMBLY__ */
 #endif	/* _LINUX_IOPORT_H */
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 24c3956..bad433f 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -265,6 +265,8 @@ static inline int get_page_unless_zero(struct page *page)
 	return atomic_inc_not_zero(&page->_count);
 }
 
+extern int page_is_ram(unsigned long pfn);
+
 /* Support for virtually mapped pages */
 struct page *vmalloc_to_page(const void *addr);
 unsigned long vmalloc_to_pfn(const void *addr);

  reply	other threads:[~2010-02-02  1:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  3:21 [PATCH 0/3] generic hotplug friendly page_is_ram() Wu Fengguang
2010-01-22  3:21 ` [PATCH 1/3] resources: introduce generic page_is_ram() Wu Fengguang
2010-01-22  4:10   ` KAMEZAWA Hiroyuki
2010-01-22  4:20     ` [PATCH 1/3 v3] " Wu Fengguang
2010-01-22  5:15   ` [PATCH 1/3] " Xiaotian Feng
2010-01-22  5:37     ` Wu Fengguang
2010-01-22  5:50       ` Xiaotian Feng
2010-01-22  5:52         ` Wu Fengguang
2010-01-22  7:51   ` H. Peter Anvin
2010-01-22  8:16     ` [PATCH 1/3 v4] " Wu Fengguang
2010-01-27  0:30       ` Andrew Morton
2010-01-27  3:06         ` Wu Fengguang
2010-02-02  1:01           ` tip-bot for Wu Fengguang [this message]
2010-01-22  3:21 ` [PATCH 2/3] x86: remove bios data range from e820 Wu Fengguang
2010-01-22  4:06   ` Wu Fengguang
2010-01-27  0:32   ` Andrew Morton
2010-02-02  1:01   ` [tip:x86/mm] x86: Remove BIOS " tip-bot for Yinghai Lu
2010-01-22  3:21 ` [PATCH 3/3] x86: use the generic page_is_ram() Wu Fengguang
2010-02-02  1:01   ` [tip:x86/mm] x86: Use " tip-bot for Wu Fengguang

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=tip-53df8fdc15fb646b0219e43c989c2cdab1ab100c@git.kernel.org \
    --to=fengguang.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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