[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <562F5EA8.2070507@linaro.org>
Date: Tue, 27 Oct 2015 12:23:20 +0100
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Matthias Brugger <matthias.bgg@...il.com>,
Yingjoe Chen <yingjoe.chen@...iatek.com>
Cc: djkurtz@...omium.org, sboyd@...eaurora.org, tglx@...utronix.de,
jamesjj.liao@...iatek.com, linux@....linux.org.uk,
srv_heupstream@...iatek.com, arnd@...db.de,
catalin.marinas@....com, kernel@...gutronix.de,
"open list:CLOCKSOURCE, CLOC..." <linux-kernel@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC..."
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek@...ts.infradead.org>,
Kevin Hilman <khilman@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH V2] clockevents/drivers/mtk: Fix spurious interrupt
leading to crash
On 10/27/2015 12:11 PM, Matthias Brugger wrote:
> Hi Daniel,
>
> On 26/08/15 16:25, Daniel Lezcano wrote:
>> On 08/25/2015 03:21 PM, Yingjoe Chen wrote:
>>> Tested-by: Yingjoe Chen<yingjoe.chen@...iatek.com>
>>
>> Applied to my tree for 4.4.
>>
>> -- Daniel
>>
>
> Kevin found a regression in v4.3 which will need this patch to fix it
> [1]. Can you apply it to your clockevents/4.3-fixes branch please.
>
> Thanks,
> Matthias
>
> [1] https://lkml.org/lkml/2015/10/26/211
Hmm, I thought it wasn't impacting 4.3, so it went to 4.4.
Let me look how to backport this fix without introducing a conflict when
tip/timers/urgent will be merged to tip/timers/core.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
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