From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] IA64: Use early_parm to handle mvec_name and nomca
Date: Mon, 13 Mar 2006 08:12:41 +0000 [thread overview]
Message-ID: <20060313081241.GA2160@verge.net.au> (raw)
In-Reply-To: <20060310082445.GA18715@verge.net.au>
On Sun, Mar 12, 2006 at 10:33:27PM -0800, Chen, Kenneth W wrote:
> Horms wrote on Sunday, March 12, 2006 8:08 PM
> > IA64: Use early_parm to handle mvec_name and nomca
> >
> > I'm not sure of the worthiness of this idea, so please consider it an RFC.
> > Its key merits are:
> >
> > * Reuse existing infrastructure
> > * Greatly tightens up the parsing of nomca
> > * Greatly simplifies the parsing of machvec
>
> It is kind of odd though that parse_early_param() is called twice,
> once from init/main.c:start_kernel and once from arch/ia64/kernel/
> setup.c:setup_arch. Though you are not the one introduces that
> Oddity.
Yes, that is odd. I guess the arch/ia64/kernel/setup.c one could be
removed. That is, unless the init/main.c is called too late. I'll
investigate that.
> The other thing is that the code you changed are going to be thrown
> away after initialization, so I take your motivation of the patch
> is in some form of uncluttered the source code?
Yes. It seems to me that the parsing is greatly simplified with this
approach.
> If I were you, I would put machvec code into machvec.c, like this:
That is an excellent idea.
--
Horms
prev parent reply other threads:[~2006-03-13 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 8:24 [RFC] IA64: Use early_parm to handle mvec_name and nomca Horms
2006-03-10 9:54 ` Jes Sorensen
2006-03-11 3:43 ` Horms
2006-03-11 8:51 ` Jes Sorensen
2006-03-11 20:17 ` Chen, Kenneth W
2006-03-13 4:08 ` Horms
2006-06-02 11:48 ` IA64: Broken Serial Console Horms
2006-06-02 11:53 ` Matthew Wilcox
2006-06-04 4:57 ` Horms
2006-06-02 11:59 ` Francois WELLENREITER
2006-03-13 6:33 ` [RFC] IA64: Use early_parm to handle mvec_name and nomca Chen, Kenneth W
2006-03-13 8:12 ` Horms [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=20060313081241.GA2160@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox