Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756014Ab3EYD3m (ORCPT ); Fri, 24 May 2013 23:29:42 -0400 Received: from mail-pa0-f47.google.com ([209.85.220.47]:57712 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755409Ab3EYD3l (ORCPT ); Fri, 24 May 2013 23:29:41 -0400 Message-ID: <51A0301C.3020206@gmail.com> Date: Sat, 25 May 2013 11:29:32 +0800 From: Zhang Yanfei User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120607 Thunderbird/10.0.5 MIME-Version: 1.0 To: "Eric W. Biederman" , Vivek Goyal , Andrew Morton , Ralf Baechle , Simon Horman CC: "kexec@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: [PATCH 4/7] mips: Remove savemaxmem parameter setup References: <51A02E50.5020507@gmail.com> In-Reply-To: <51A02E50.5020507@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1288 Lines: 44 From: Zhang Yanfei saved_max_pfn is used to know the amount of memory that the previous kernel used. And for powerpc, we set saved_max_pfn by passing the kernel commandline parameter "savemaxmem=". The only user of saved_max_pfn in mips is read_oldmem interface. Since we have removed read_oldmem, so we don't need this parameter anymore. Signed-off-by: Zhang Yanfei Cc: Ralf Baechle --- arch/mips/kernel/crash_dump.c | 10 ---------- 1 files changed, 0 insertions(+), 10 deletions(-) diff --git a/arch/mips/kernel/crash_dump.c b/arch/mips/kernel/crash_dump.c index 3be9e7b..f291cf9 100644 --- a/arch/mips/kernel/crash_dump.c +++ b/arch/mips/kernel/crash_dump.c @@ -4,16 +4,6 @@ #include #include -static int __init parse_savemaxmem(char *p) -{ - if (p) - saved_max_pfn = (memparse(p, &p) >> PAGE_SHIFT) - 1; - - return 1; -} -__setup("savemaxmem=", parse_savemaxmem); - - static void *kdump_buf_page; /** -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/