From: trini@kernel.crashing.org
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: [patch 11/22] __early_param for m68knommu
Date: Wed, 24 Mar 2004 18:59:33 -0500 [thread overview]
Message-ID: <20040324235933.RFQI4381.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/m68knommu/kernel/setup.c | 3 +--
linux-2.6-early_setup-trini/arch/m68knommu/kernel/vmlinux.lds.S | 3 +++
2 files changed, 4 insertions(+), 2 deletions(-)
diff -puN arch/m68knommu/kernel/setup.c~m68knommu arch/m68knommu/kernel/setup.c
--- linux-2.6-early_setup/arch/m68knommu/kernel/setup.c~m68knommu 2004-03-24 16:15:07.785434583 -0700
+++ linux-2.6-early_setup-trini/arch/m68knommu/kernel/setup.c 2004-03-24 16:15:07.790433457 -0700
@@ -226,8 +226,7 @@ void setup_arch(char **cmdline_p)
/* Keep a copy of command line */
*cmdline_p = &command_line[0];
- memcpy(saved_command_line, command_line, sizeof(saved_command_line));
- saved_command_line[sizeof(saved_command_line)-1] = 0;
+ parse_early_options(cmdline_p);
#ifdef DEBUG
if (strlen(*cmdline_p))
diff -puN arch/m68knommu/kernel/vmlinux.lds.S~m68knommu arch/m68knommu/kernel/vmlinux.lds.S
--- linux-2.6-early_setup/arch/m68knommu/kernel/vmlinux.lds.S~m68knommu 2004-03-24 16:15:07.787434133 -0700
+++ linux-2.6-early_setup-trini/arch/m68knommu/kernel/vmlinux.lds.S 2004-03-24 16:15:07.790433457 -0700
@@ -262,6 +262,9 @@ SECTIONS {
__setup_start = .;
*(.init.setup)
__setup_end = .;
+ __early_begin = .;
+ __early_param : { *(__early_param) }
+ __early_end = .;
__start___param = .;
*(__param)
__stop___param = .;
_
reply other threads:[~2004-03-25 0:04 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=20040324235933.RFQI4381.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®