From: Andrew Morton <akpm@osdl.org>
To: trini@kernel.crashing.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 1/22] Add __early_param for all arches
Date: Wed, 24 Mar 2004 19:55:02 -0800 [thread overview]
Message-ID: <20040324195502.00a5b148.akpm@osdl.org> (raw)
In-Reply-To: <20040324235722.QDLK23486.fed1mtao04.cox.net@localhost.localdomain>
trini@kernel.crashing.org wrote:
>
> Hello. The following is outcome of talking with David Woodhouse about
> the need in various parts of the kernel to parse the command line very
> early and set some options based on what we read. The result is
> __early_param("arg", fn) based very heavily on the macro of the same name
> in the arm kernel. The following is the core of these changes, adding the
> macro, struct and externs to <linux/init.h>, the parser to init/main.c
> and converting console= to this format. As a follow on to this thread are
> patches against all arches (vs 2.6.5-rc2) to use the global define of
> saved_command_line, add the appropriate bits to
> arch/$(ARCH)/kernel/vmlinux.lds.S and in some cases, convert params
> from the old arch-specific variant to the new __early_param way.
I don't recall seeing this requirement mentioned before, and that's a ton
of patches you have there.
Please tell us a little more about why we need these patches. (Apart from
what seems to be a moderate amount of code consolidation).
Also, what is different between __setup and __early_setup? Why is it not
possible to make __setup run sufficiently early for whatever application is
requiring these changes?
Thanks.
next prev parent reply other threads:[~2004-03-25 3:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 23:57 [patch 1/22] Add __early_param for all arches trini
2004-03-25 3:55 ` Andrew Morton [this message]
2004-03-26 11:29 ` David Woodhouse
2004-03-26 21:03 ` Russell King
2004-03-26 21:15 ` David Woodhouse
2004-03-31 4:23 ` Rusty Russell
2004-03-31 16:13 ` Tom Rini
2004-04-01 1:51 ` Rusty Russell
2004-04-01 2:24 ` Tom Rini
2004-04-01 2:56 ` Rusty Russell
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=20040324195502.00a5b148.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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.