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
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <562F6437.1000507@linaro.org>
Date:	Tue, 27 Oct 2015 12:47:03 +0100
From:	Daniel Lezcano <daniel.lezcano@...aro.org>
To:	Yingjoe Chen <yingjoe.chen@...iatek.com>, tglx@...utronix.de
Cc:	Matthias Brugger <matthias.bgg@...il.com>, djkurtz@...omium.org,
	sboyd@...eaurora.org, 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>
Subject: Re: [PATCH V2] clockevents/drivers/mtk: Fix spurious interrupt
 leading to crash

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<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.

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


-- 
  <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

Powered by Openwall GNU/*/Linux Powered by OpenVZ