linux-kernel - [PATCH v2 0/2] More GIC updates for Linux 4.4

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: <1444822037-16983-1-git-send-email-marc.zyngier@arm.com>
Date:	Wed, 14 Oct 2015 12:27:15 +0100
From:	Marc Zyngier <marc.zyngier@....com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Jason Cooper <jason@...edaemon.net>
Cc:	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>,
	Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>,
	Duc Dang <dhdang@....com>
Subject: [PATCH v2 0/2] More GIC updates for Linux 4.4

Hi Thomas,

Here's a couple of GIC patches that I'd like to see in 4.4:

- A fix for a (copy-paste) bug introduced by the fwnode/fwspec
  conversion, breaking LPI translation

- An extension to the GICv2m driver, enabling support for multiple MSI
  frames (already posted)

This is on top of tip/irq/core as of yesterday. Hopefully, this is the
last set of GIC patches for the next merge window (and I really mean
it this time).

Thanks,

	M.

* From v1:
  - Fixed the add_tree/create_tree resolution issue in the GICv2m patch

Marc Zyngier (2):
  irqchip/gic-v3: Fix translation of LPIs after conversion to irq_fwspec
  irqchip/gic-v2m: Add support for multiple MSI frames

 drivers/irqchip/irq-gic-v2m.c | 124 ++++++++++++++++++++++++++----------------
 drivers/irqchip/irq-gic-v3.c  |  22 +++++---
 2 files changed, 91 insertions(+), 55 deletions(-)

-- 
2.1.4

--
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/