linux-kernel - [PATCH] Remove "unused variable" warning in arch/x86/xen/setup.c on UP systems.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 17 May 2008 09:41:10 +0530
From:	"Manish Katiyar" <mkatiyar@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>, trivial@...r.kernel.org,
	kernel-janitors@...r.kernel.org
Subject: [PATCH] Remove "unused variable" warning in arch/x86/xen/setup.c on UP systems.

On UP systems cpu_data is defined as boot_cpu_data, due to which we
get the below error while compiling xen.

CC      arch/x86/xen/setup.o
arch/x86/xen/setup.c: In function 'xen_enable_sysenter':
arch/x86/xen/setup.c:74: warning: unused variable 'cpu'

The below patch defines the variable only when SMP is defined.


Signed-off-by : Manish Katiyar <mkatiyar@...il.com>

diff -Nur a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
--- a/arch/x86/xen/setup.c       2008-04-26 20:36:15.000000000 +0530
+++ b/arch/x86/xen/setup.c        2008-05-17 09:30:12.000000000 +0530
@@ -71,7 +71,9 @@

 void xen_enable_sysenter(void)
 {
+#ifdef CONFIG_SMP
        int cpu = smp_processor_id();
+#endif
        extern void xen_sysenter_target(void);
        /* Mask events on entry, even though they get enabled immediately */
        static struct callback_register sysenter = {


-- 
Thanks & Regards,
********************************************
Manish Katiyar ( http://mkatiyar.googlepages.com )
3rd Floor, Fair Winds Block
EGL Software Park
Off Intermediate Ring Road
Bangalore 560071, India
***********************************************
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/