From: tip-bot for Javier Martinez Canillas <martinez.javier@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
gorcunov@openvz.org, rakib.mullick@gmail.com,
martinez.javier@gmail.com, ebiederm@xmission.com, tj@kernel.org,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/apic] x86/apic/es7000_32: Remove unused variable
Date: Thu, 8 Jul 2010 07:17:33 GMT [thread overview]
Message-ID: <tip-5bbd4a336c81d32df71642abf310cf3d0c98dc9b@git.kernel.org> (raw)
In-Reply-To: <1278546719.9020.4.camel@lenovo>
Commit-ID: 5bbd4a336c81d32df71642abf310cf3d0c98dc9b
Gitweb: http://git.kernel.org/tip/5bbd4a336c81d32df71642abf310cf3d0c98dc9b
Author: Javier Martinez Canillas <martinez.javier@gmail.com>
AuthorDate: Wed, 7 Jul 2010 19:51:59 -0400
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Thu, 8 Jul 2010 09:14:37 +0200
x86/apic/es7000_32: Remove unused variable
In today's linux-next I got this compile warning:
arch/x86/kernel/apic/es7000_32.c:132: warning: 'base' defined but not used
Current patch solves the issue removing the unused variable.
Signed-off-by: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Tejun Heo <tj@kernel.org>
LKML-Reference: <1278546719.9020.4.camel@lenovo>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/apic/es7000_32.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/apic/es7000_32.c b/arch/x86/kernel/apic/es7000_32.c
index 425e53a..8593582 100644
--- a/arch/x86/kernel/apic/es7000_32.c
+++ b/arch/x86/kernel/apic/es7000_32.c
@@ -129,7 +129,6 @@ int es7000_plat;
* GSI override for ES7000 platforms.
*/
-static unsigned int base;
static int __cpuinit wakeup_secondary_cpu_via_mip(int cpu, unsigned long eip)
{
parent reply other threads:[~2010-07-08 7:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1278546719.9020.4.camel@lenovo>]
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-5bbd4a336c81d32df71642abf310cf3d0c98dc9b@git.kernel.org \
--to=martinez.javier@gmail.com \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.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=rakib.mullick@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@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
Powered by JetHome