linux-kernel - Re: [PATCH v2] clocksource: timer-sp804: Fix read_current_timer() issue when clock source is not registered

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: <65bfb302-3e93-4d1f-a70c-66439cf5f122@kernel.org>
Date: Tue, 8 Apr 2025 20:52:18 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Stephen Eta Zhou <stephen.eta.zhou@...look.com>,
 Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: "tglx@...utronix.de" <tglx@...utronix.de>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] clocksource: timer-sp804: Fix read_current_timer()
 issue when clock source is not registered

On 08/04/2025 09:00, Stephen Eta Zhou wrote:
> Hi all,
> 
> Just pinging this patch, it's been about a month since I sent out v2,
> but I haven't received any feedback yet.
> 
> If there are any issues with this patch, feel free to let me know. Thanks!
It does not look like patch at all - it has duplicated From and Subject.
Please read submitting patches. The patch fails this in multiple places.

What's more the actual patch is corrupted, so could not be even applied.
You can try by yourself to apply it and see.

Anyway, follow closely submitting patches.

About the actual problem: I don't understand how commit msg is related
to it.

Best regards,
Krzysztof