Hi Sasha,

> -----Original Message-----
> From: Sasha Levin [mailto:[email protected]]
> Sent: Wednesday, December 19, 2018 4:25 AM
> To: Sasha Levin <[email protected]>; Daniel Lezcano 
> <[email protected]>; Alexey Brodkin <[email protected]>;
> [email protected]
> Cc: [email protected]; Daniel Lezcano <[email protected]>; 
> Vineet Gupta <[email protected]>;
> Thomas Gleixner <[email protected]>; [email protected]; 
> [email protected]
> Subject: Re: [PATCH 12/25] clocksource/drivers/arc_timer: Utilize generic 
> sched_clock
> 
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
> 
> The bot has tested the following trees: v4.19.10, v4.14.89, v4.9.146, 
> v4.4.168, v3.18.130,
> 
> v4.19.10: Build OK!
> v4.14.89: Failed to apply! Possible dependencies:
>     Unable to calculate

Here we just need a bit updated hunk due to missing [1] which was only 
introduced in v4.15:
-------------------------->8------------------------
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -299,6 +299,7 @@ config CLKSRC_MPS2
 config ARC_TIMERS
        bool "Support for 32-bit TIMERn counters in ARC Cores" if COMPILE_TEST
        depends on GENERIC_CLOCKEVENTS
+       depends on GENERIC_SCHED_CLOCK
        select TIMER_OF
        help
          These are legacy 32-bit TIMER0 and TIMER1 counters found on all ARC 
cores
-------------------------->8------------------------

> v4.9.146: Failed to apply! Possible dependencies:
> v4.4.168: Failed to apply! Possible dependencies:
> v3.18.130: Failed to apply! Possible dependencies:

Everything below v4.10 we'll need to drop as ARC timers were only imported in 
v4.10, see [2].

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f8a26c166eba01382765bc2fa575387e41079ac
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c4c9a040ecb7297e011e579f5a9cc280e42d725f

-Alexey

Reply via email to