Message ID | CACRpkdZGze_2=hWe414Eum_9hpNXgog5vmu6Y4R_zhg0x2z0SQ@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Thu, Feb 19, 2015 at 9:48 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote: > David Miller <davem@davemloft.net> writes: > >>> Now if you can make it in -rc2 or -rc3, this revert should be forgotten. But if >>> you can't make it for 3.20, I'll push for the revert. >>> >>> So I think it's up to you now, and let's see what Gregh says about it. >> >> What is the current status of this? I'd like to see this move forward so we >> can get this fixed ASAP. > Hi David, > > Linus has submitted the patch [1]. I'll be watching carefully until -rc4 that > this is applied. If it's not, I'll reping you to apply this revert. Until then, > you can forget about it, I'll do the follow-up. > [1] https://lkml.org/lkml/2015/2/18/310 Looping in Greg and Grant so they know we are waiting for their verdict on that patch... Yours, Liunus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
On Fri, Feb 20, 2015 at 4:33 PM, Greg KH <gregkh@linuxfoundation.org> wrote: > On Fri, Feb 20, 2015 at 10:37:59AM +0100, Linus Walleij wrote: >> On Thu, Feb 19, 2015 at 9:48 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote: >> > David Miller <davem@davemloft.net> writes: >> > >> >>> Now if you can make it in -rc2 or -rc3, this revert should be forgotten. But if >> >>> you can't make it for 3.20, I'll push for the revert. >> >>> >> >>> So I think it's up to you now, and let's see what Gregh says about it. >> >> >> >> What is the current status of this? I'd like to see this move forward so we >> >> can get this fixed ASAP. >> > Hi David, >> > >> > Linus has submitted the patch [1]. I'll be watching carefully until -rc4 that >> > this is applied. If it's not, I'll reping you to apply this revert. Until then, >> > you can forget about it, I'll do the follow-up. >> > [1] https://lkml.org/lkml/2015/2/18/310 >> >> Looping in Greg and Grant so they know we are waiting for their verdict >> on that patch... > > I have no idea what you are talking about here :( It is a patch to drivers/base, which I'm waiting for you to look at... The link to the patch was right above, here it is again :) https://lkml.org/lkml/2015/2/18/310 Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
diff --git a/drivers/base/platform.c b/drivers/base/platform.c index 9421fed40905..301f4b9ae908 100644 --- a/drivers/base/platform.c +++ b/drivers/base/platform.c @@ -101,6 +101,15 @@ int platform_get_irq(struct platform_device *dev, unsigned int num) } r = platform_get_resource(dev, IORESOURCE_IRQ, num); + /* + * The resources may pass trigger flags to the irqs that need + * to be set up. It so happens that the trigger flags for + * IORESOURCE_BITS correspond 1-to-1 to the IRQF_TRIGGER* + * settings. + */ + if (r->flags & IORESOURCE_BITS) + irqd_set_trigger_type(irq_get_irq_data(r->start), + r->flags & IORESOURCE_BITS);