All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <Yinghai.Lu@Sun.COM>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Travis <travis@sgi.com>,
	Christoph Lameter <clameter@sgi.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] x86_64: should use array directly for early_ptr
Date: Wed, 23 Jan 2008 01:27:31 -0800	[thread overview]
Message-ID: <200801230127.32113.yinghai.lu@sun.com> (raw)
In-Reply-To: <200801230056.16424.yinghai.lu@sun.com>

[PATCH] x86_64: should use array directly for early_ptr

Signed-off-by: Yinghai Lu <yinghai.lu@sun.com>

--- a/arch/x86/kernel/setup_64.c	2008-01-23 01:21:06.000000000 -0800
+++ b/arch/x86/kernel/setup_64.c	2008-01-23 01:21:24.000000000 -0800
@@ -344,10 +344,10 @@
 
 #ifdef CONFIG_SMP
 	/* setup to use the early static init tables during kernel startup */
-	x86_cpu_to_apicid_early_ptr = (void *)&x86_cpu_to_apicid_init;
-	x86_bios_cpu_apicid_early_ptr = (void *)&x86_bios_cpu_apicid_init;
+	x86_cpu_to_apicid_early_ptr = (void *)x86_cpu_to_apicid_init;
+	x86_bios_cpu_apicid_early_ptr = (void *)x86_bios_cpu_apicid_init;
 #ifdef CONFIG_NUMA
-	x86_cpu_to_node_map_early_ptr = (void *)&x86_cpu_to_node_map_init;
+	x86_cpu_to_node_map_early_ptr = (void *)x86_cpu_to_node_map_init;
 #endif
 #endif
 

  reply	other threads:[~2008-01-23  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23  8:56 [PATCH] x86_64: remove duplicated line about x86_bios_cpu_apicid_early_ptr Yinghai Lu
2008-01-23  9:27 ` Yinghai Lu [this message]
2008-01-23 14:18   ` [PATCH] x86_64: should use array directly for early_ptr Mike Travis
2008-01-23 14:16 ` [PATCH] x86_64: remove duplicated line about x86_bios_cpu_apicid_early_ptr Mike Travis
2008-01-23 14:37   ` Mike Travis

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=200801230127.32113.yinghai.lu@sun.com \
    --to=yinghai.lu@sun.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=travis@sgi.com \
    /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.