[<prev] [next>] [day] [month] [year] [list]
Message-ID: <tip-0mbwou1zt7pafij09b897lg3@git.kernel.org>
Date: Tue, 10 Dec 2013 15:03:38 -0800
From: "tip-bot for H. Peter Anvin" <tipbot@...or.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
stable@...r.kernel.org, kevin.b.smith@...el.com,
sunil.k.pandey@...el.com, tglx@...utronix.de, hpa@...ux.intel.com
Subject: [tip:x86/urgent] x86, build, icc: Remove uninitialized_var()
from compiler-intel.h
Commit-ID: 503cf95c061a0551eb684da364509297efbe55d9
Gitweb: http://git.kernel.org/tip/503cf95c061a0551eb684da364509297efbe55d9
Author: H. Peter Anvin <hpa@...ux.intel.com>
AuthorDate: Tue, 10 Dec 2013 14:56:06 -0800
Committer: H. Peter Anvin <hpa@...ux.intel.com>
CommitDate: Tue, 10 Dec 2013 15:01:01 -0800
x86, build, icc: Remove uninitialized_var() from compiler-intel.h
When compiling with icc, <linux/compiler-gcc.h> ends up included
because the icc environment defines __GNUC__. Thus, we neither need
nor want to have this macro defined in both compiler-gcc.h and
compiler-intel.h, and the fact that they are inconsistent just makes
the compiler spew warnings.
Reported-by: Sunil K. Pandey <sunil.k.pandey@...el.com>
Cc: Kevin B. Smith <kevin.b.smith@...el.com>
Signed-off-by: H. Peter Anvin <hpa@...ux.intel.com>
Link: http://lkml.kernel.org/n/tip-0mbwou1zt7pafij09b897lg3@git.kernel.org
Cc: <stable@...r.kernel.org>
---
include/linux/compiler-intel.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/compiler-intel.h b/include/linux/compiler-intel.h
index 973ce10..dc1bd3d 100644
--- a/include/linux/compiler-intel.h
+++ b/include/linux/compiler-intel.h
@@ -28,8 +28,6 @@
#endif
-#define uninitialized_var(x) x
-
#ifndef __HAVE_BUILTIN_BSWAP16__
/* icc has this, but it's called _bswap16 */
#define __HAVE_BUILTIN_BSWAP16__
--
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/
Powered by blists - more mailing lists