From: Sudeep Holla <sudeep.holla@arm.com>
To: daniel.lezcano@linaro.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [tip:timers/core] clocksource/drivers/arm_arch_timer: Fix bogus cpu_all_mask usage
Date: Thu, 2 Aug 2018 14:03:48 +0100 [thread overview]
Message-ID: <3fc750c9-fd3d-3a0c-ee86-b893de9ecc77@arm.com> (raw)
In-Reply-To: <tip-6777996d27dd4f0a569ed9593e78db68c6b659cd@git.kernel.org>
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@linutronix.de>
> AuthorDate: Thu, 2 Aug 2018 14:53:10 +0200
> Committer: Thomas Gleixner <tglx@linutronix.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
next parent reply other threads:[~2018-08-02 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-6777996d27dd4f0a569ed9593e78db68c6b659cd@git.kernel.org>
2018-08-02 13:03 ` Sudeep Holla [this message]
2018-08-02 13:07 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fc750c9-fd3d-3a0c-ee86-b893de9ecc77@arm.com \
--to=sudeep.holla@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®