Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 5 Mar 2003 00:51:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 5 Mar 2003 00:51:22 -0500 Received: from air-2.osdl.org ([65.172.181.6]:3779 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Wed, 5 Mar 2003 00:51:21 -0500 Message-ID: <32981.4.64.238.61.1046844111.squirrel@www.osdl.org> Date: Tue, 4 Mar 2003 22:01:51 -0800 (PST) Subject: Re: Reserving physical memory at boot time From: "Randy.Dunlap" To: In-Reply-To: References: X-Priority: 3 Importance: Normal Cc: X-Mailer: SquirrelMail (version 1.2.8) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 37 > Followup to: > By author: > "Randy.Dunlap" > In newsgroup: linux.dev.kernel >> >> Patch for 'mem=exactmap' in 2.4 was submitted several weeks ago and Alan >> merged it into -ac. It does need to be pushed to Marcelo... >> > > Once again, with feeling... > > DON'T CALL IT mem=. > > mem= is part of the boot protocol. > Call it memmap= or something, or you'll break boot loaders in weird and > subtle ways. OK, with feeling: I agree with you since the boot protocol is well-defined. Just to be clear, my comment was referring to Documentation/kernel-parameters.txt, not to any C code. And it would really be helpful to catch issues like this soon after they happen... Thanks, ~Randy - 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/