linux-kernel - [GIT PULL] irqchip: mvebu: fixes for v3.13

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]

Date:	Tue, 17 Dec 2013 09:55:18 -0500
From:	Jason Cooper <jason@...edaemon.net>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andrew Lunn <andrew@...n.ch>,
	Gregory CLEMENT <gregory.clement@...e-electrons.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: [GIT PULL] irqchip: mvebu: fixes for v3.13

Thomas,

Here's a couple of small fixes for the armada-370-xp driver.  These have
been in -next for 3 days now.

thx,

Jason.


The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:

  Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)

are available in the git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-irqchip-fixes-3.13

for you to fetch changes up to c7f7bd4a136e4b02dd2a66bf95aec545bd93e8db:

  irqchip: armada-370-xp: fix MSI race condition (2013-12-13 16:34:40 +0000)

----------------------------------------------------------------
mvebu irqchip fixes for v3.13

 - armada-370-xp
    - fix races is MSI and IPI

----------------------------------------------------------------
Lior Amsalem (2):
      irqchip: armada-370-xp: fix IPI race condition
      irqchip: armada-370-xp: fix MSI race condition

 drivers/irqchip/irq-armada-370-xp.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
--
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/