public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
	linux kernel <linux-kernel@vger.kernel.org>,
	Matt Mackall <mpm@selenic.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] init: support preset lpj value as config option
Date: Fri, 26 Jan 2007 10:29:24 -0800	[thread overview]
Message-ID: <45BA4884.4020205@am.sony.com> (raw)
In-Reply-To: <20070126024411.4d4b6c2e.akpm@osdl.org>

Andrew Morton wrote:
>> i386 is missing CONFIG_CMDLINE support, and this architecture
>> is used in embedded.
> 
> So if we add CONFIG_CMDLINE we fix this problem and we bring i386 into line
> with other platforms.  It's all good.
> 
>>  I think many other x86 derivatives are
>> also missing .config-based command line support.  CELF has
>> worked to get patches submitted to fix this, but so far these
>> haven't been accepted.
> 
> You have?
> 
> <looks at inbox>
> 
> To whom?

Matt Mackall would know better than I.  He's the person
CELF hired to do this.  Here are some of the previous LKML
discussions around this issue:

http://lkml.org/lkml/2006/6/11/115

http://lkml.org/lkml/2006/7/31/208

Last time I talked to Matt about this (some time in
November, I believe), he said he had worked out a
solution agreeable to H. Peter Anvin, who had issues
with the original submission.  I'm not sure if that
latest solution was submitted to mainline or not.

Matt?
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================


  reply	other threads:[~2007-01-26 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  0:12 [PATCH] init: support preset lpj value as config option Tim Bird
2007-01-25  2:18 ` Paul Mundt
2007-01-25 18:24   ` Tim Bird
2007-01-26 10:44     ` Andrew Morton
2007-01-26 18:29       ` Tim Bird [this message]
2007-01-26 18:46         ` Matt Mackall
2007-01-26 19:02           ` H. Peter Anvin

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=45BA4884.4020205@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=akpm@osdl.org \
    --cc=hpa@zytor.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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