linux-kernel - Re: [PATCH] mfd: arizona: convert to regmap_add_irq

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 31 Jul 2012 18:22:29 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>, linux-kernel@...r.kernel.org,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH] mfd: arizona: convert to regmap_add_irq_chips

On Tue, Jul 31, 2012 at 11:20:53AM -0600, Stephen Warren wrote:

> I agree in general, but I don't see how this is a regression in this
> change - the arizona pdata doesn't specify an IRQ base anywhere, and
> hence the IRQ base is already dynamically allocated...

> The (regmap-irq) API (in the patch I sent) does support optionally
> specifying a base if you want, it's just that the arizona-irq.c patch I
> sent didn't specify a base, since the original code didn't.

I see.  It sounded like the regmap patch had the regression, not the
device specific patch.
--
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/