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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 04 Nov 2006 10:29:37 -0800
From:	William D Waddington <william.waddington@...zmo.com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH] IRQ: ease out-of-tree migration to new irq_handler prototype

From: william.waddington@...zmo.com

Ease out-of-tree driver migration to new irq_handler prototype.
Define empty 3rd argument macro for use in multi kernel version
out-of-tree drivers going forward.  Backportable drives can do:

(in a header)
#ifndef __PT_REGS
# define __PT_REGS , struct pt_regs *regs
#endif

(in code body)
static irqreturn_t irq_handler(int irq, void *dev_id __PT_REGS)

Signed-off-by: Bill Waddington <william.waddington@...zmo.com>

---

Has this suggestion by Ingo Molnar been implemented?  May I
submit it?  Is this how it's done?

--- 2.6.19-rc3/include/linux/interrupt.h.ORIG	2006-11-04 
09:15:16.000000000 -0800
+++ 2.6.19-rc3/include/linux/interrupt.h	2006-11-04 09:23:18.000000000 -0800
@@ -66,6 +66,14 @@

  typedef irqreturn_t (*irq_handler_t)(int, void *);

+/*
+ * Irq handler migration helper - empty 3rd argument
+ * #define __PT_REGS , struct pt_regs *regs
+ * for older kernel versions
+ */
+
+#define __PT_REGS
+
  struct irqaction {
  	irq_handler_t handler;
  	unsigned long flags;


Bill
-- 
--------------------------------------------
William D Waddington
Bainbridge Island, WA, USA
william.waddington@...zmo.com
--------------------------------------------
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch
-
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