From: "Randy.Dunlap" <rddunlap@osdl.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] kernel-parameters.txt
Date: Mon, 07 Mar 2005 00:51:07 +0000 [thread overview]
Message-ID: <422BA57B.1050409@osdl.org> (raw)
In-Reply-To: <422A58AB.8040601@osdl.org>
Eamonn Lachlan wrote:
> Randy wrote:
>
>> ... [Documentation/x86_64/boot-options.txt]
>>should be merged into kernel-parameters.txt,
>>with indications that they are X86-64 only.
>
>
> I'll have a look at merging the two files first, then,
> alright?
Sounds good/right to me, but please check with Andi Kleen
(ak@suse.de) to see if he will merge it, so that you don't
waste your time.
> A quick grep of the arch trees in 2.6.11 says there are
>
> 1 arch/alpha 1 arch/ppc
> 11 arch/arm 9 arch/ppc64
> 5 arch/arm26 5 arch/s390
> 21 arch/i386 4 arch/sh
> 12 arch/ia64 2 arch/sh64
> 1 arch/m32r 1 arch/sparc
> 3 arch/mips 8 arch/um
> 2 arch/parisc 22 arch/x86_64
>
> so many occurences of "__setup(".
>
> But in the kernel-parameters.txt file, I only see only
> four params with a PPC* arch flag where I would expect
> to find ten.
>
> There seem to be a lot missing. :)
>
> Should I hunt the missing params down in their arch trees
> and add them in?
Yes, that's would I would prefer to see, but again, I don't
want you wasting time on it if it won't be merged.
--
~Randy
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-03-07 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 1:11 [KJ] kernel-parameters.txt Randy.Dunlap
2005-03-06 4:46 ` Eamonn Lachlan
2005-03-06 19:38 ` Randy.Dunlap
2005-03-07 0:17 ` Eamonn Lachlan
2005-03-07 0:51 ` 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=422BA57B.1050409@osdl.org \
--to=rddunlap@osdl.org \
--cc=kernel-janitors@vger.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.