mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Rob Landley <rob@landley.net>,
	lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>,
	bos@serpentine.com, werner@almesberger.net
Subject: Re: [PATCH] docs: ramdisk/initrd/initramfs corrections
Date: Fri, 31 Aug 2007 01:41:35 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708310139460.22832@localhost.localdomain> (raw)
In-Reply-To: <20070830161316.b04f041d.randy.dunlap@oracle.com>

On Thu, 30 Aug 2007, Randy Dunlap wrote:

> On Thu, 30 Aug 2007 15:41:27 -0700 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=<ram_size>" has been changed to
> > >>> "ramdisk_size=<ram_size>" to make it clearer.  The original
> > >>> "ramdisk=<ram_size>" 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.
>
> I couldn't find it.  Can you provide a pointer to it?

sure.  http://marc.info/?l=linux-kernel&m=118828410509208&w=2
>
> > > 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.)
>
> Peter, what are you objecting to, Rob's comment, Robert's comment,
> Robert's patch, or my patch?

i'm sure he's objecting to my aforementioned patch.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

  parent reply	other threads:[~2007-08-31  5:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 18:20 Randy Dunlap
2007-08-30 18:28 ` Robert P. J. Day
2007-08-30 23:36   ` Rob Landley
2007-08-30 22:41     ` H. Peter Anvin
2007-08-30 23:13       ` Randy Dunlap
2007-08-30 23:21         ` H. Peter Anvin
2007-08-31  5:41         ` Robert P. J. Day [this message]
2007-08-31  5:34       ` Robert P. J. Day
2007-09-02  8:26       ` Geert Uytterhoeven
2007-08-31  7:29     ` Robert P. J. Day
2007-08-31 14:25     ` Valdis.Kletnieks
2007-08-31 14:20       ` Robert P. J. Day
2007-08-30 19:13 ` Bryan O'Sullivan
2007-08-30 23:29 ` Rob Landley
2007-08-31  0:00 ` Jesper Juhl

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=Pine.LNX.4.64.0708310139460.22832@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=akpm@linux-foundation.org \
    --cc=bos@serpentine.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rob@landley.net \
    --cc=werner@almesberger.net \
    /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

all inboxes | Powered by JetHome®