public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: dsaxena@plexity.net
Cc: Matt Mackall <mpm@selenic.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	ak@suse.de
Subject: Re: [PATCH] x86_64 built-in command line
Date: Mon, 31 Jul 2006 20:47:28 -0700	[thread overview]
Message-ID: <44CECED0.8010503@zytor.com> (raw)
In-Reply-To: <20060801010652.GA17771@plexity.net>

Deepak Saxena wrote:
> On Jul 31 2006, at 12:14, Matt Mackall was caught saying:
>> Allow setting a command line at build time on x86_64. Compiled but not
>> tested.
> 
> Can we just make this into a generic option and put the relevant strcpy
> (strcat) in init/main.c. We've supported a default in-kernel command line
> on ARM for sometime now and I think it would be best to just have a single
> implementation.
> 

Yes on the generic option, no on putting it in init/main.c... on a lot 
of architectures, some parsing of the command line happens *very* early, 
sometimes even before the C code is invoked.

	-hpa

      parent reply	other threads:[~2006-08-01  3:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 17:14 [PATCH] x86_64 built-in command line Matt Mackall
2006-07-31 17:46 ` linux-os (Dick Johnson)
2006-07-31 20:07 ` Andi Kleen
2006-07-31 20:41   ` H. Peter Anvin
2006-07-31 22:17     ` Andi Kleen
2006-08-01  1:43       ` Matt Mackall
2006-08-01  2:29         ` H. Peter Anvin
2006-08-01  2:33         ` H. Peter Anvin
2006-08-01  2:38         ` H. Peter Anvin
2006-08-01  2:41           ` Matt Mackall
2006-08-01  2:44             ` Andi Kleen
2006-08-01  2:46               ` H. Peter Anvin
2006-08-01  2:46                 ` Andi Kleen
2006-08-01  2:46             ` H. Peter Anvin
2006-08-01  2:49         ` Andrew Morton
2006-08-01  1:06 ` Deepak Saxena
2006-08-01  1:18   ` Andi Kleen
2006-08-01  3:47   ` H. Peter Anvin [this message]

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=44CECED0.8010503@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dsaxena@plexity.net \
    --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