linux-kernel - Re: [tip: timers/clocksource] clocksource/drivers/exynos_mct: Don't register as a sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87qzy6q6sj.ffs@tglx>
Date: Thu, 24 Jul 2025 11:25:48 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org, Daniel
 Lezcano <daniel.lezcano@...aro.org>
Cc: linux-tip-commits@...r.kernel.org, Donghoon Yu <hoony.yu@...sung.com>,
 Youngmin Nam <youngmin.nam@...sung.com>, John Stultz <jstultz@...gle.com>,
 Will McVicker <willmcvicker@...gle.com>, x86@...nel.org
Subject: Re: [tip: timers/clocksource] clocksource/drivers/exynos_mct: Don't
 register as a sched_clock on arm64

On Thu, Jul 24 2025 at 07:20, Ingo Molnar wrote:
> * Ingo Molnar <mingo@...nel.org> wrote:
>
>> The whole SOB chain of this commit is messy and has several serious 
>> problems:
>
> Not just this commit, but most of the other commits in 
> tip:timers/clocksource have various problems in their tag sections ... 
> I only checked these more closely:
>
>  5d86e479193b clocksource/drivers/exynos_mct: Add module support
>  60618eec98f0 clocksource/drivers/exynos_mct: Fix uninitialized irq name warning
>  10934da577f6 clocksource/drivers/exynos_mct: Set local timer interrupts as percpu
>  394b981382e6 clocksource/drivers/exynos_mct: Don't register as a sched_clock on arm64
>
> but all of them have various problems. And literally all 23 commits 
> have the Link tag misplaced in the middle of the tag section.

Duh. I did not check when pulling that lot.