[RFC PATCH 25/28] signal: use CONFIG_X86_32 instead of __i386__

From: Octavian Purdila
Date: Tue Nov 03 2015 - 15:24:58 EST


Signed-off-by: Octavian Purdila <octavian.purdila@xxxxxxxxx>
---
kernel/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/signal.c b/kernel/signal.c
index 0f6bbbe..0367131 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -1137,7 +1137,7 @@ static void print_fatal_signal(int signr)
struct pt_regs *regs = signal_pt_regs();
printk(KERN_INFO "potentially unexpected fatal signal %d.\n", signr);

-#if defined(__i386__) && !defined(__arch_um__)
+#ifdef CONFIG_X86_32
printk(KERN_INFO "code at %08lx: ", regs->ip);
{
int i;
--
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/