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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 13 Nov 2012 20:56:37 +0100
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	broonie@...nsource.wolfsonmicro.com, swarren@...dia.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework
 for interrupt

Hi Laxman,

On Tue, Nov 13, 2012 at 07:33:55PM +0530, Laxman Dewangan wrote:
> This patch series has following change:
> - Use regmap irq framework for interrupt registration. Corrected the
>   register bit definition for interrupts.
> - Move the irq table to tps65910.c and get rid of tps65910-irq.c.
> - Raarrange the init sequence of different sub moduled of tps65910 like
>   irq, clock and then mfd devices.
> - Export the irq domain handle from regmap to use in mfd driver.
> - Pass the irq domain in mfd_add_devices to have proper interrupt mapping
>   for sub devices like RTC.
> 
> 
> Changes from V1: 
> - rearrange patch on which older patch3 become the new patch 1.
> - Add stub for new api in the regmap.
> - Add empty line if paragraph change in description.
> 
> Changes from V2:
> - Remove the older 4th patch where API for getting irq_domain was added
>   in regmap. It is already taken care by Mark B.
The patchset looks fine, but it should either go through Mark's tree or I
should merge Mark's regmap_irq_get_domain patch to my for-next branch.
Mark, any preference ?

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ