From: Thomas Gleixner <tglx@linutronix.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Frederic Weisbecker <frederic@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [PATCH 02/10] clockevents: Shutdown and unregister current clockevents at CPUHP_AP_TICK_DYING
Date: Thu, 31 Oct 2024 14:09:31 +0100 [thread overview]
Message-ID: <87ldy4wh9w.ffs@tglx> (raw)
In-Reply-To: <82382d49-cbd1-4a03-9402-bc7d41bca9b9@samsung.com>
On Thu, Oct 31 2024 at 13:16, Marek Szyprowski wrote:
> On 29.10.2024 13:54, Frederic Weisbecker wrote:
> This patch landed in today's linux-next as commit c80e6e9de6ae
> ("clockevents: Shutdown and unregister current clockevents at
> CPUHP_AP_TICK_DYING"). Unfortunately it breaks booting most of my test
> systems (ARM 32bit, ARM 64bit and RISC-V 64bit). Reverting $subject on
> top of linux-next (and fixing the merge conflict) seems to be restoring
> proper boot sequence. Here is a log observed on QEMU's ARM64 'virt' machine:
It's fixed already. Refetch the branch (force updated).
Thanks,
tglx
next prev parent reply other threads:[~2024-10-31 13:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 12:54 [PATCH 00/10] clockevents: Rearrange cpuhotplug operations v2 Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 01/10] clockevents: Improve clockevents_notify_released() comment Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 02/10] clockevents: Shutdown and unregister current clockevents at CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-31 12:16 ` [PATCH 02/10] " Marek Szyprowski
2024-10-31 13:09 ` Thomas Gleixner [this message]
2024-10-29 12:54 ` [PATCH 03/10] tick: Remove now unneeded low-res tick stop on CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 04/10] ARM: smp_twd: Remove clockevents shutdown call on offlining Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 05/10] clocksource/drivers/arm_arch_timer: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 06/10] clocksource/drivers/arm_global_timer: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 07/10] clocksource/drivers/exynos_mct: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 08/10] clocksource/drivers/armada-370-xp: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 09/10] clocksource/drivers/qcom: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 10/10] clocksource/drivers/timer-tegra: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 16:50 [PATCH 00/10] clockevents: Rearrange cpuhotplug operations Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 02/10] clockevents: Shutdown and unregister current clockevents at CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-21 5:00 ` kernel test robot
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=87ldy4wh9w.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.