Re: [PATCH V2] clockevents/drivers/mtk: Fix spurious interrupt leading to crash
From: Daniel Lezcano
Date: Tue Oct 27 2015 - 07:47:13 EST
On 10/27/2015 12:23 PM, Daniel Lezcano wrote:
On 10/27/2015 12:11 PM, Matthias Brugger wrote:
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@xxxxxxxxxxxx>
Applied to my tree for 4.4.
Kevin found a regression in v4.3 which will need this patch to fix it
. Can you apply it to your clockevents/4.3-fixes branch please.
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.
do you think I can cherry-pick from tip/timers/core or clockevents/4.4
directly the fix to be pulled into clockevents/4.3-fixes ? That will
certainly raise a conflict when tip/timers/urgent will be merged to
tip/timers/core (a trivial conflict actually).
<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 |
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/