From: trini@kernel.crashing.org
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: [patch 5/22] __early_param for alpha
Date: Wed, 24 Mar 2004 18:58:18 -0500 [thread overview]
Message-ID: <20040324235818.RFEO4381.fed1mtao07.cox.net@localhost.localdomain> (raw)
- Remove saved_command_line (and saving of the command line).
- Call parse_early_options
---
linux-2.6-early_setup-trini/arch/alpha/kernel/setup.c | 3 +--
linux-2.6-early_setup-trini/arch/alpha/kernel/vmlinux.lds.S | 5 +++++
2 files changed, 6 insertions(+), 2 deletions(-)
diff -puN arch/alpha/kernel/setup.c~alpha arch/alpha/kernel/setup.c
--- linux-2.6-early_setup/arch/alpha/kernel/setup.c~alpha 2004-03-24 16:15:06.043826820 -0700
+++ linux-2.6-early_setup-trini/arch/alpha/kernel/setup.c 2004-03-24 16:15:06.048825694 -0700
@@ -115,7 +115,6 @@ static void get_sysnames(unsigned long,
char **, char **);
static char command_line[COMMAND_LINE_SIZE];
-char saved_command_line[COMMAND_LINE_SIZE];
/*
* The format of "screen_info" is strange, and due to early
@@ -527,8 +526,8 @@ setup_arch(char **cmdline_p)
} else {
strlcpy(command_line, COMMAND_LINE, sizeof command_line);
}
- strcpy(saved_command_line, command_line);
*cmdline_p = command_line;
+ parse_early_options(cmdline_p);
/*
* Process command-line arguments.
diff -puN arch/alpha/kernel/vmlinux.lds.S~alpha arch/alpha/kernel/vmlinux.lds.S
--- linux-2.6-early_setup/arch/alpha/kernel/vmlinux.lds.S~alpha 2004-03-24 16:15:06.045826370 -0700
+++ linux-2.6-early_setup-trini/arch/alpha/kernel/vmlinux.lds.S 2004-03-24 16:15:06.049825469 -0700
@@ -45,6 +45,11 @@ SECTIONS
__setup_end = .;
. = ALIGN(8);
+ __early_begin = .;
+ __early_param : { *(__early_param) }
+ __early_end = .;
+
+ . = ALIGN(8);
__start___param = .;
__param : { *(__param) }
__stop___param = .;
_
reply other threads:[~2004-03-25 0:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040324235818.RFEO4381.fed1mtao07.cox.net@localhost.localdomain \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®