From: Borislav Petkov <bp@alien8.de>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, Qian Cai <cai@lca.pw>,
Thomas Gleixner <tglx@linutronix.de>,
Waiman Long <longman@redhat.com>, x86 <x86@kernel.org>
Subject: Re: [tip: timers/core] Revert "tick/common: Make tick_periodic() check for missing ticks"
Date: Thu, 19 Mar 2020 21:10:28 +0100 [thread overview]
Message-ID: <20200319201028.GF13073@zn.tnic> (raw)
In-Reply-To: <158464406295.28353.3230662958771714087.tip-bot2@tip-bot2>
On Thu, Mar 19, 2020 at 06:54:22PM -0000, tip-bot2 for Thomas Gleixner wrote:
> The following commit has been merged into the timers/core branch of tip:
>
> Commit-ID: 52da479a9aee630d2cdf37d05edfe5bcfff3e17f
> Gitweb: https://git.kernel.org/tip/52da479a9aee630d2cdf37d05edfe5bcfff3e17f
> Author: Thomas Gleixner <tglx@linutronix.de>
> AuthorDate: Thu, 19 Mar 2020 19:47:06 +01:00
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitterDate: Thu, 19 Mar 2020 19:47:48 +01:00
>
> Revert "tick/common: Make tick_periodic() check for missing ticks"
>
> This reverts commit d441dceb5dce71150f28add80d36d91bbfccba99 due to
> boot failures.
>
> Reported-by: Qian Cai <cai@lca.pw>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Waiman Long <longman@redhat.com>
> ---
> kernel/time/tick-common.c | 36 +++---------------------------------
> 1 file changed, 3 insertions(+), 33 deletions(-)
ACK, this fixes an early boot freeze on one of my boxes too.
Tested-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2020-03-19 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 18:54 [tip: timers/core] Revert "tick/common: Make tick_periodic() check for missing ticks" tip-bot2 for Thomas Gleixner
2020-03-19 20:10 ` Borislav Petkov [this message]
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=20200319201028.GF13073@zn.tnic \
--to=bp@alien8.de \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=longman@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).