Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764024AbXHaFrd (ORCPT ); Fri, 31 Aug 2007 01:47:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760670AbXHaFrK (ORCPT ); Fri, 31 Aug 2007 01:47:10 -0400 Received: from nic.NetDirect.CA ([216.16.235.2]:55360 "EHLO rubicon.netdirect.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759332AbXHaFrI (ORCPT ); Fri, 31 Aug 2007 01:47:08 -0400 X-Originating-Ip: 72.143.66.27 Date: Fri, 31 Aug 2007 01:34:55 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: "H. Peter Anvin" cc: Rob Landley , Randy Dunlap , lkml , akpm , bos@serpentine.com, werner@almesberger.net Subject: Re: [PATCH] docs: ramdisk/initrd/initramfs corrections In-Reply-To: <46D74797.4070105@zytor.com> Message-ID: References: <20070830112055.2b2c8985.randy.dunlap@oracle.com> <200708301836.48707.rob@landley.net> <46D74797.4070105@zytor.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Net-Direct-Inc-MailScanner-Information: Please contact the ISP for more information X-Net-Direct-Inc-MailScanner: Found to be clean X-Net-Direct-Inc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-16.8, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -15.00, INIT_RECVD_OUR_AUTH -20.00, RCVD_IN_SORBS_DUL 20.00) X-Net-Direct-Inc-MailScanner-From: rpjday@mindspring.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1670 Lines: 45 On Thu, 30 Aug 2007, H. Peter Anvin wrote: > Rob Landley wrote: > > On Thursday 30 August 2007 1:28:17 pm Robert P. J. Day wrote: > > > On Thu, 30 Aug 2007, Randy Dunlap wrote: > > > > > > ... > > > > > > > The old "ramdisk=" has been changed to > > > > "ramdisk_size=" to make it clearer. The original > > > > "ramdisk=" has been kept around for compatibility reasons, > > > > but it may be removed in the future. > > > ... > > > > > > i just the other day submitted a patch to remove that backward > > > compatibility, and the m68k portion of it has already been acked by > > > geert uytterhoeven. > > > > Could you mention it in feature-removal-schedule.txt? (People > > check that for warning of upcoming changes that impact existing > > code. They may not notice something elsewhere after they've got > > it working...) > > > > The same objection applies to this as to the previous one. In that > respect, an Ack from a maintainer of an almost unused architecture > is meaningless (sorry, Geert.) fair enough, but since i posted that patch to LKML three days ago, someone *could* have NAKed it at the time. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== - 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/