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
| ||
|
Date: Thu, 13 Mar 2014 19:03:50 +0100 From: Hans de Goede <hdegoede@...hat.com> To: Thomas Gleixner <tglx@...utronix.de>, Maxime Ripard <maxime.ripard@...e-electrons.com> Cc: linux-arm-kernel@...ts.infradead.org, devicetree <devicetree@...r.kernel.org>, linux-kernel@...r.kernel.org, linux-sunxi@...glegroups.com Subject: [PATCH v3 0/4] irq: sun4i IRQ 0 / ENMI fixes Hi All, Here is v3 of my sun4i IRQ 0 / ENMI fixes patch-set, changelog below: v2: PATCH 1/4 irq: Add handle_fasteoi_late_irq irq handler New patch by Thomas Gleixner, adding a new irq handler with the "call eoi after the irq-handler has run its course" behavior we need to avoid double irqs on the ENMI. PATCH 2/4 irqchip: sun4i: Fix irq 0 not working Modified to avoid spurious calls to the irq 0 handler, as suggested by Maxime. PATCH 3/4 irqchip: sun4i: Fix a comment about mask register Added Maxime's Acked-by PATCH 4/4 irqchip: sun4i: Use handle_fasteoi_late_irq for the New patch switching the handler for irq 0 over to the new handle_fasteoi_late_irq handler, thereby fixing the double interrupts issue v3: PATCH 1/4 irq: Add a new IRQCHIP_EOI_THREADED flag New patch by Thomas Gleixner, replacing his "irq: Add handle_fasteoi_late_irq irq handler" patch. PATCH 2/4 irqchip: sun4i: Fix irq 0 not working Added Maxime's Acked-by PATCH 4/4 irqchip: sun4i: Don't ack IRQs != 0, fix acking of IRQ New patch replacing my "irqchip: sun4i: Use handle_fasteoi_late_irq ..." patch. This also drops acking for IRQ != 0. I've done both changes in one patch to avoid regressing for IRQ 0. Thanks for all the help to all involved. Regards, Hans -- 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