public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] x86 built-in command line (resend)
Date: Mon, 31 Jul 2006 12:35:16 -0700	[thread overview]
Message-ID: <44CE5B74.4060409@zytor.com> (raw)
In-Reply-To: <20060731192844.GK6908@waste.org>

Matt Mackall wrote:
> On Mon, Jul 31, 2006 at 12:07:02PM -0700, H. Peter Anvin wrote:
>> Matt Mackall wrote:
>>> I'm resending this as-is because the earlier thread petered out
>>> without any strong arguments against this approach. x86_64 patch to
>>> follow.
>> "No strong arguments?"
>>
>> I still maintain that this patch has the wrong priority in case more 
>> than one set of arguments are provided.
> 
> But you still haven't answered how that lets you work around firmware
> that passes parameters you don't like.
> 

That a fairly unique problem, and is most likely in a minority 
application.  For that case a CONFIG option to ignore the 
firmware-provided command line would make sense.  I do not believe it 
should be the only option or even the default.

It would be particularly good if this could be standardized across 
architectures, which is another reason to do it right.

	-hpa


  reply	other threads:[~2006-07-31 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 17:13 [PATCH] x86 built-in command line (resend) Matt Mackall
2006-07-31 18:48 ` Roman Zippel
2006-07-31 19:07 ` H. Peter Anvin
2006-07-31 19:28   ` Matt Mackall
2006-07-31 19:35     ` H. Peter Anvin [this message]
2006-07-31 20:57       ` Matt Mackall

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=44CE5B74.4060409@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@osdl.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