From: tip-bot for Tejun Heo <tj@kernel.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
yinghai@kernel.org, tj@kernel.org, tglx@linutronix.de,
mingo@elte.hu
Subject: [tip:x86/numa] x86: Rename incorrectly named parameter of numa_cpu_node()
Date: Mon, 31 Jan 2011 17:24:47 GMT [thread overview]
Message-ID: <tip-eff9073790e1286aa12bf1c65814d3e0132b12e1@git.kernel.org> (raw)
In-Reply-To: <20110131155905.GM7459@htj.dyndns.org>
Commit-ID: eff9073790e1286aa12bf1c65814d3e0132b12e1
Gitweb: http://git.kernel.org/tip/eff9073790e1286aa12bf1c65814d3e0132b12e1
Author: Tejun Heo <tj@kernel.org>
AuthorDate: Mon, 31 Jan 2011 16:59:05 +0100
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 31 Jan 2011 18:22:25 +0100
x86: Rename incorrectly named parameter of numa_cpu_node()
numa_cpu_node() prototype in numa_32.h has wrongly named
parameter @apicid when it actually takes the CPU number.
Change it to @cpu.
Reported-by: Yinghai Lu <yinghai@kernel.org>
Signed-off-by: Tejun Heo <tj@kernel.org>
LKML-Reference: <20110131155905.GM7459@htj.dyndns.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/include/asm/numa_32.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/include/asm/numa_32.h b/arch/x86/include/asm/numa_32.h
index bc66031..c6beed1 100644
--- a/arch/x86/include/asm/numa_32.h
+++ b/arch/x86/include/asm/numa_32.h
@@ -6,7 +6,7 @@ extern int numa_off;
extern int pxm_to_nid(int pxm);
#ifdef CONFIG_NUMA
-extern int __cpuinit numa_cpu_node(int apicid);
+extern int __cpuinit numa_cpu_node(int cpu);
#else /* CONFIG_NUMA */
static inline int numa_cpu_node(int cpu) { return NUMA_NO_NODE; }
#endif /* CONFIG_NUMA */
prev parent reply other threads:[~2011-01-31 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 15:59 [PATCH tip/x86/numa] x86: Rename incorrectly named parameter of numa_cpu_node() Tejun Heo
2011-01-31 17:24 ` tip-bot for Tejun Heo [this message]
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=tip-eff9073790e1286aa12bf1c65814d3e0132b12e1@git.kernel.org \
--to=tj@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 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.