linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-next@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: linux-next: manual merge of the boot-params tree
Date: Tue, 30 Dec 2008 01:22:31 +1100	[thread overview]
Message-ID: <20081230012231.fcd112cd.sfr@canb.auug.org.au> (raw)

Hi Rusty,

Today's linux-next merge of the boot-params tree got a conflict in
init/main.c between commit 0b8f1efad30bd58f89961b82dfe68b9edf8fd2ac
("sparse irq_desc[] array: core kernel and x86 changes") from the
sparseirq tree and commit 25bf48b74b9fb23b347d00656b604f9e55c72183 ("Fix
powerpc (tested on ppc64) command line handling") from the boot-params
tree.

Just overlapping additions.  I fixed it up (see below) and can carry the
fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc init/main.c
index 396b271,ad933ad..0000000
--- a/init/main.c
+++ b/init/main.c
@@@ -543,20 -522,30 +526,40 @@@ void __init __weak thread_info_cache_in
  {
  }
  
 +int __init __weak arch_early_irq_init(void)
 +{
 +	return 0;
 +}
 +
 +int __init __weak early_irq_init(void)
 +{
 +	return arch_early_irq_init();
 +}
 +
+ /* Non-destructive early parse of commandline.  PowerPC calls this early. */
+ void __init parse_early_and_core_params(char *cmdline)
+ {
+ 	static bool __initdata done = false;
+ 
+ 	if (done)
+ 		return;
+ 
+ 	parse_args("Core and early params", cmdline,
+ 		   __start___core_param,
+ 		   __stop___core_param - __start___core_param,
+ 		   do_early_param, true);
+ 	done = true;
+ }
+ 
  asmlinkage void __init start_kernel(void)
  {
- 	char * command_line;
- 	extern struct kernel_param __start___param[], __stop___param[];
+ 	char *static_command_line;
+ 
+ 	printk(KERN_NOTICE);
+ 	printk(linux_banner);
+ 
+ 	arch_get_boot_command_line();
+ 	parse_early_and_core_params(boot_command_line);
  
  	smp_setup_processor_id();
  

             reply	other threads:[~2008-12-29 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 14:22 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-29 14:10 linux-next: manual merge of the boot-params tree Stephen Rothwell
2008-12-29 21:22 ` Rusty Russell
2008-12-29 14:01 Stephen Rothwell
2008-12-18  9:35 Stephen Rothwell
2008-12-15 13:21 Stephen Rothwell
2008-12-15 13:21 Stephen Rothwell
2008-12-15 13:20 Stephen Rothwell
2008-12-15 13:20 Stephen Rothwell

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=20081230012231.fcd112cd.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).