[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tip-959c071f0974cda7702d7574647de7ad9259eb57@git.kernel.org>
Date: Fri, 8 Nov 2013 15:09:53 -0800
From: tip-bot for Seiji Aguchi <tipbot@...or.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
seiji.aguchi@....com, tglx@...utronix.de, hpa@...ux.intel.com
Subject: [tip:x86/trace] x86, trace: Remove __alloc_intr_gate()
Commit-ID: 959c071f0974cda7702d7574647de7ad9259eb57
Gitweb: http://git.kernel.org/tip/959c071f0974cda7702d7574647de7ad9259eb57
Author: Seiji Aguchi <seiji.aguchi@....com>
AuthorDate: Wed, 30 Oct 2013 16:36:08 -0400
Committer: H. Peter Anvin <hpa@...ux.intel.com>
CommitDate: Fri, 8 Nov 2013 14:15:44 -0800
x86, trace: Remove __alloc_intr_gate()
Prepare to move set_intr_gate() into a macro by removing
__alloc_intr_gate().
The purpose is to avoid failing a kernel build after applying a
subsequent patch which changes set_intr_gate() into a macro.
Signed-off-by: Seiji Aguchi <seiji.aguchi@....com>
Link: http://lkml.kernel.org/r/52716DB8.1080702@hds.com
Signed-off-by: H. Peter Anvin <hpa@...ux.intel.com>
---
arch/x86/include/asm/desc.h | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/x86/include/asm/desc.h b/arch/x86/include/asm/desc.h
index b90e5df..d939567 100644
--- a/arch/x86/include/asm/desc.h
+++ b/arch/x86/include/asm/desc.h
@@ -395,15 +395,10 @@ static inline void trace_set_intr_gate(unsigned int gate, void *addr)
#define __trace_alloc_intr_gate(n, addr)
#endif
-static inline void __alloc_intr_gate(unsigned int n, void *addr)
-{
- set_intr_gate(n, addr);
-}
-
#define alloc_intr_gate(n, addr) \
do { \
alloc_system_vector(n); \
- __alloc_intr_gate(n, addr); \
+ set_intr_gate(n, addr); \
__trace_alloc_intr_gate(n, trace_##addr); \
} while (0)
--
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