public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Yanfei <zhangyanfei.yes@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Simon Horman <horms@verge.net.au>,
	Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 6/7] ia64: Remove setting for saved_max_pfn
Date: Sat, 25 May 2013 11:33:50 +0800	[thread overview]
Message-ID: <51A0311E.8030105@gmail.com> (raw)
In-Reply-To: <51A02E50.5020507@gmail.com>

From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>

The only user of saved_max_pfn in ia64 is read_oldmem interface but we
have removed that interface, so saved_max_pfn is now unneeded in ia64,
and we needn't set it anymore.

Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: Matt Fleming <matt.fleming@intel.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
---
 arch/ia64/kernel/efi.c |    5 -----
 1 files changed, 0 insertions(+), 5 deletions(-)

diff --git a/arch/ia64/kernel/efi.c b/arch/ia64/kernel/efi.c
index f034563..51bce59 100644
--- a/arch/ia64/kernel/efi.c
+++ b/arch/ia64/kernel/efi.c
@@ -1116,11 +1116,6 @@ efi_memmap_init(u64 *s, u64 *e)
 		if (!is_memory_available(md))
 			continue;
 
-#ifdef CONFIG_CRASH_DUMP
-		/* saved_max_pfn should ignore max_addr= command line arg */
-		if (saved_max_pfn < (efi_md_end(md) >> PAGE_SHIFT))
-			saved_max_pfn = (efi_md_end(md) >> PAGE_SHIFT);
-#endif
 		/*
 		 * Round ends inward to granule boundaries
 		 * Give trimmings to uncached allocator
-- 
1.7.1

  parent reply	other threads:[~2013-05-25  3:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  3:21 [PATCH 0/7] Remove unused /dev/oldmem interface Zhang Yanfei
2013-05-25  3:24 ` [PATCH 1/7] /dev/oldmem: Remove the interface Zhang Yanfei
2013-05-25  3:26 ` [PATCH 2/7] Documentation/devices.txt: Remove /dev/oldmem description Zhang Yanfei
2013-05-25 23:20   ` Eric W. Biederman
2013-05-26  0:58     ` Zhang Yanfei
2013-05-27  1:27       ` HATAYAMA Daisuke
2013-05-27  1:27         ` Zhang Yanfei
2013-05-29 22:20           ` Andrew Morton
2013-05-30  5:49             ` Zhang Yanfei
2013-05-25  3:27 ` [PATCH 3/7] Documentation/kdump/kdump.txt: " Zhang Yanfei
2013-05-25  3:29 ` [PATCH 4/7] mips: Remove savemaxmem parameter setup Zhang Yanfei
2013-05-25  3:31 ` [PATCH 5/7] powerpc: " Zhang Yanfei
2013-05-25  3:33 ` Zhang Yanfei [this message]
2013-05-25  3:36 ` [PATCH 7/7] s390: Remove setting for saved_max_pfn Zhang Yanfei
2013-05-25  7:11 ` [PATCH 0/7] Remove unused /dev/oldmem interface H. Peter Anvin
2013-05-25 23:25 ` Eric W. Biederman
2013-05-28 14:37   ` Vivek Goyal
2013-05-28 15:11     ` H. Peter Anvin
2013-05-29 22:11       ` Andrew Morton
2013-05-28 19:00     ` Eric W. Biederman
2013-05-29 16:10       ` Vivek Goyal

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=51A0311E.8030105@gmail.com \
    --to=zhangyanfei.yes@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=fenghua.yu@intel.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=tony.luck@intel.com \
    --cc=vgoyal@redhat.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