public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] documentation: add more early_param boot options
Date: Fri, 22 Aug 2008 12:13:57 -0700	[thread overview]
Message-ID: <48AF0FF5.1020007@oracle.com> (raw)
In-Reply-To: <86802c440808221207k726a7eb5p67e2333818fe4303@mail.gmail.com>

Yinghai Lu wrote:
> On Fri, Aug 22, 2008 at 12:02 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Add some (more) early_param boot options to kernel-parameters.txt.
>>
>> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
>> ---
>>  Documentation/kernel-parameters.txt |   12 ++++++++++++
>>  1 file changed, 12 insertions(+)
>>
>> --- lin2627-rc4.orig/Documentation/kernel-parameters.txt
>> +++ lin2627-rc4/Documentation/kernel-parameters.txt
>> @@ -129,6 +129,13 @@ and is between 256 and 4096 characters.
>>  ./include/asm/setup.h as COMMAND_LINE_SIZE.
>>
>>
>> +       additional_cpus=  [IA-64,X86-32,X86-64]
>> +                       Format: <int>
>> +                       Specify the number of additional hotplug CPUs that
>> +                       should be supported/allowed.  Can be used to
>> +                       override BIOS info or to provide this info if not
>> +                       already available.
>> +
> how about the one in Documentation/x86/x86_64/boot-options.txt ?

Oh.  Thanks.  I'll think about how to handle that (or drop that part)
and respin/resend it.


      reply	other threads:[~2008-08-22 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 19:02 [PATCH] documentation: add more early_param boot options Randy Dunlap
2008-08-22 19:07 ` Yinghai Lu
2008-08-22 19:13   ` Randy Dunlap [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=48AF0FF5.1020007@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yhlu.kernel@gmail.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