[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87qzxznzjp.ffs@tglx>
Date: Tue, 29 Jul 2025 10:58:50 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Daniel Lezcano <daniel.lezcano@...aro.org>, Ingo Molnar <mingo@...nel.org>
Cc: linux-kernel@...r.kernel.org, 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, Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org>, Arnd Bergmann <arnd@...nel.org>
Subject: Re: [tip: timers/clocksource] clocksource/drivers/exynos_mct: Don't
register as a sched_clock on arm64
On Tue, Jul 29 2025 at 09:58, Daniel Lezcano wrote:
> just a gentle ping for the question below about dropping the two patches.
>
> On 25/07/2025 15:15, Daniel Lezcano wrote:
>
> [ ... ]
>
>>> So I got no answer for this question, but I suppose my assumption is
>>> correct - so I've rebased the tip:timers/clocksource commits to fix the
>>> misattribution and a number of other problems, and also fixed various
>>> typos, spelling mistakes and inconsistencies in the changelogs while at
>>> it. Let me know if I got something wrong.
>>
>> If the rebase is possible, I suggest to take the opportunity to remove
>> the following patches:
>>
>> commit 5d86e479193b - clocksource/drivers/exynos_mct: Add module support
>> commit 7e477e9c4eb4 - clocksource/drivers/exynos_mct: Fix section
>> mismatch from the module conversion
>>
>> Because of:
>>
>> [1] https://lore.kernel.org/all/20250725090349.87730-2-
>> krzysztof.kozlowski@...aro.org/
>>
>> [2] https://lore.kernel.org/all/bccb77b9-7cdc-4965-
>> aa05-05836466f81f@....fastmail.com/
Grrr.
I've already sent the pull request for the pile. Let me ask Linus not to
pull and I revert them on top.
Also please reset your clockevents branch so next does not have the
conflicting SHAs
Thanks,
tglx
Powered by blists - more mailing lists