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
| ||
|
Date: Mon, 20 Dec 2010 13:23:44 +0900 From: Paul Mundt <lethal@...ux-sh.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Samuel Ortiz <sameo@...ux.intel.com>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Sundar Iyer <sundar.iyer@...ricsson.com>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Linus Walleij <linus.walleij@...aro.org> Subject: Re: linux-next: manual merge of the mfd tree with the ux500-core tree On Mon, Dec 20, 2010 at 03:21:48PM +1100, Stephen Rothwell wrote: > The genirq core is being converted to pass struct irq_data to irq_chip > operations rather than an IRQ number. Update the tc35892 driver to the > new APIs. > > Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com> > Acked-by: Rabin Vincent <rabin.vincent@...ricsson.com> > Signed-off-by: Samuel Ortiz <sameo@...ux.intel.com> Sorry to hijack the thread.. > diff --git a/drivers/mfd/tc3589x.c b/drivers/mfd/tc3589x.c > index 32291fe..dde2d858 100644 > --- a/drivers/mfd/tc3589x.c > +++ b/drivers/mfd/tc3589x.c > @@ -170,15 +170,15 @@ again: > return IRQ_HANDLED; > } > > -static void tc3589x_irq_dummy(unsigned int irq) > +static void tc3589x_irq_dummy(struct irq_data *data) > { > /* No mask/unmask at this level */ > } > > static struct irq_chip tc3589x_irq_chip = { > - .name = "tc3589x", > - .mask = tc3589x_irq_dummy, > - .unmask = tc3589x_irq_dummy, > + .name = "tc3589x", > + .irq_mask = tc3589x_irq_dummy, > + .irq_unmask = tc3589x_irq_dummy, > }; > > static int tc3589x_irq_init(struct tc3589x *tc3589x) Is there some reason you don't just kill this off and use dummy_irq_chip? -- 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