From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754394AbbJ0LrI (ORCPT ); Tue, 27 Oct 2015 07:47:08 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:33784 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754260AbbJ0LrG (ORCPT ); Tue, 27 Oct 2015 07:47:06 -0400 Subject: Re: [PATCH V2] clockevents/drivers/mtk: Fix spurious interrupt leading to crash To: Yingjoe Chen , tglx@linutronix.de References: <1440426924.17418.11.camel@mtksdaap41> <1440453450-21203-1-git-send-email-daniel.lezcano@linaro.org> <1440508871.29634.1.camel@mtksdaap41> <55DDCC4B.7010203@linaro.org> <562F5BE9.30200@gmail.com> <562F5EA8.2070507@linaro.org> Cc: Matthias Brugger , djkurtz@chromium.org, sboyd@codeaurora.org, jamesjj.liao@mediatek.com, linux@arm.linux.org.uk, srv_heupstream@mediatek.com, arnd@arndb.de, catalin.marinas@arm.com, kernel@pengutronix.de, "open list:CLOCKSOURCE, CLOC..." , "moderated list:ARM/Mediatek SoC..." , "moderated list:ARM/Mediatek SoC..." , Kevin Hilman From: Daniel Lezcano Message-ID: <562F6437.1000507@linaro.org> Date: Tue, 27 Oct 2015 12:47:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <562F5EA8.2070507@linaro.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/27/2015 12:23 PM, Daniel Lezcano wrote: > 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 >>> >>> 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. Thomas, 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). -- Daniel -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog