linux-kernel - [PATCH 0/4] Convert WM8350 to genirq

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: <20100105135756.GA2993@rakim.wolfsonmicro.main>
Date:	Tue, 5 Jan 2010 13:57:56 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org,
	Alessandro Zummo <a.zummo@...ertech.it>,
	rtc-linux@...glegroups.com
Subject: [PATCH 0/4] Convert WM8350 to genirq

The following patch series converts the WM8350 driver to use genirq for
the interrupt controller on the chip.  It also includes a patch for the
RTC driver to handle the fact that genirq nests enables and disables.
Ideally this patch would go in via the MFD tree to avoid merge issues.

Since this collides with (and removes the need for) Dan Carpenter's
bounds checking change I've also included that in the series.

Dan Carpenter (1):
      mfd: WM8350 off by one bug

Mark Brown (3):
      mfd: Add a data argument to the WM8350 IRQ free function
      rtc: Suppress duplicate enable/disable of WM8350 update interrupt
      mfd: Convert WM8350 to genirq

 drivers/mfd/wm8350-irq.c             |  155 +++++++++++++++++++---------------
 drivers/power/wm8350_power.c         |   24 +++---
 drivers/regulator/wm8350-regulator.c |    2 +-
 drivers/rtc/rtc-wm8350.c             |   11 ++-
 include/linux/mfd/wm8350/core.h      |   45 +++++++---
 include/linux/mfd/wm8350/rtc.h       |    1 +
 sound/soc/codecs/wm8350.c            |    4 +-
 7 files changed, 144 insertions(+), 98 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/