[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <3fc750c9-fd3d-3a0c-ee86-b893de9ecc77@arm.com>
Date: Thu, 2 Aug 2018 14:03:48 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: daniel.lezcano@...aro.org, hpa@...or.com,
linux-kernel@...r.kernel.org, mingo@...nel.org, tglx@...utronix.de,
linux-tip-commits@...r.kernel.org
Cc: Sudeep Holla <sudeep.holla@....com>
Subject: Re: [tip:timers/core] clocksource/drivers/arm_arch_timer: Fix bogus
cpu_all_mask usage
On 02/08/18 13:57, tip-bot for Thomas Gleixner wrote:
> Commit-ID: 6777996d27dd4f0a569ed9593e78db68c6b659cd
> Gitweb: https://git.kernel.org/tip/6777996d27dd4f0a569ed9593e78db68c6b659cd
> Author: Thomas Gleixner <tglx@...utronix.de>
> AuthorDate: Thu, 2 Aug 2018 14:53:10 +0200
> Committer: Thomas Gleixner <tglx@...utronix.de>
> CommitDate: Thu, 2 Aug 2018 14:55:52 +0200
>
> clocksource/drivers/arm_arch_timer: Fix bogus cpu_all_mask usage
>
> Using cpu_all_mask as target mask for clockevents is wrong as it never can
> actually target not possible CPUs. Use cpu_possible_mask instead
>
I think this was already merged for v4.18 as:
Commit 5e18e412973d ("clocksource: arm_arch_timer: Set arch_mem_timer
cpumask to cpu_possible_mask")
I assume you have earlier -rc as base for tip tree and you might have
missed it.
--
Regards,
Sudeep
Powered by blists - more mailing lists