All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Yinghai Lu" <yinghai@kernel.org>, Ralf Baechle <ralf@linux-mips.org>
Cc: "Hugh Dickins" <hugh@veritas.com>, "Ingo Molnar" <mingo@elte.hu>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, "Paul Mackerras" <paulus@samba.org>,
	"Benjamin Herrenschmidt" <benh@au1.ibm.com>
Subject: Re: linux-next: parsing mem=700M broken
Date: Thu, 1 Jan 2009 14:12:56 +1030	[thread overview]
Message-ID: <200901011412.57707.rusty@rustcorp.com.au> (raw)
In-Reply-To: <86802c440812271807q3decd21i5da99754d708449d@mail.gmail.com>

On Sunday 28 December 2008 12:37:59 Yinghai Lu wrote:
> On Sat, Dec 27, 2008 at 4:43 PM, Hugh Dickins <hugh@veritas.com> wrote:
> > I have to wonder if all this comes too late in the cycle for 2.6.29:
> > changing the early param handling of all the arches is difficult,
> > and apparently hasn't been much tested in the short time that it's
> > been out there in linux-next.  But of course, not for me to decide.
> 
> should be ok, just need to go over all early_param()

Yes, and understanding the intricacies of all 20+ archs boot code.
For example, I've just noticed that MIPS sets up the command line
in prom_init, called from setup_arch, so I've broken that entirely.

git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-boot-params.git

This is not going to make this merge window: I need to audit each arch
more deeply, then get help testing.

Thanks,
Rusty.

  reply	other threads:[~2009-01-01  3:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23  3:06 linux-next: parsing mem=700M broken Hugh Dickins
2008-12-23  5:52 ` Yinghai Lu
2008-12-23 14:33   ` Ingo Molnar
2008-12-24  7:38     ` Rusty Russell
2008-12-24  8:09       ` Yinghai Lu
2008-12-24 23:09         ` Yinghai Lu
2008-12-25 11:40         ` Rusty Russell
2008-12-25 22:46           ` Yinghai Lu
2008-12-24 12:30       ` Ingo Oeser
2008-12-25  5:50         ` Rusty Russell
2008-12-24 14:44       ` Hugh Dickins
2008-12-25  3:28         ` Rusty Russell
2008-12-27 13:12         ` Rusty Russell
2008-12-28  0:43           ` Hugh Dickins
2008-12-28  2:07             ` Yinghai Lu
2009-01-01  3:42               ` Rusty Russell [this message]
2008-12-25 12:17     ` [RFC] boot parameter handling cleanup II Rusty Russell
2008-12-25 12:20       ` [RFC PATCH] param: start_kernel_with_args() Rusty Russell
2008-12-27 10:14       ` [RFC] boot parameter handling cleanup II Ingo Molnar

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=200901011412.57707.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=benh@au1.ibm.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=ralf@linux-mips.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yinghai@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.