linux-kernel - [PATCH] um: irq changes break build

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0610061025260.29356@sbz-30.cs.Helsinki.FI>
Date:	Fri, 6 Oct 2006 10:26:12 +0300 (EEST)
From:	Pekka J Enberg <penberg@...helsinki.fi>
To:	akpm@...l.org
cc:	linux-kernel@...r.kernel.org, dhowells@...hat.com,
	jdike@...toit.com, blaisorblade@...oo.it
Subject: [PATCH] um: irq changes break build

From: Pekka Enberg <penberg@...helsinki.fi>

Fixup broken UML build due to 7d12e780e003f93433d49ce78cfedf4b4c52adc5 "IRQ:
Maintain regs pointer globally rather than passing to IRQ handlers".

Cc: David Howells <dhowells@...hat.com>
Cc: Jeff Dike <jdike@...toit.com>
Cc: Paolo "Blaisorblade" Giarrusso <blaisorblade@...oo.it>
Signed-off-by: Pekka Enberg <penberg@...helsinki.fi>
---

 arch/um/kernel/irq.c      |    2 +-
 include/asm-um/irq_regs.h |    1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

Index: 2.6/include/asm-um/irq_regs.h
===================================================================
--- /dev/null
+++ 2.6/include/asm-um/irq_regs.h
@@ -0,0 +1 @@
+#include <asm-generic/irq_regs.h>
Index: 2.6/arch/um/kernel/irq.c
===================================================================
--- 2.6.orig/arch/um/kernel/irq.c
+++ 2.6/arch/um/kernel/irq.c
@@ -356,7 +356,7 @@ void forward_interrupts(int pid)
 unsigned int do_IRQ(int irq, union uml_pt_regs *regs)
 {
        irq_enter();
-       __do_IRQ(irq, (struct pt_regs *)regs);
+       __do_IRQ(irq);
        irq_exit();
        return 1;
 }
-
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/