Re: [PATCH] clocksource: Update registration failure behavior documentation
From: Thomas Gleixner
Date: Wed Feb 11 2026 - 08:10:14 EST
On Tue, Feb 10 2026 at 10:56, Zhan Xusheng wrote:
> The documentation for clocksource registration functions has been updated
> to clarify the failure behavior. Specifically, the return value on failure
> is no longer an error code (-EBUSY). Instead, the function will issue
> warnings but always return 0 on failure, as previously successful
> registration attempts might still leave the system in an inconsistent
> state.
This changelog is completely made up. Which failure is ignored there and
whats the inconsistent state of a previous attempt?
The -EBUSY comment is a leftover from the original implementation. and
the pr_warn() about the vdso clock mode is harmless as it still leaves
the system in a consistent state. Just the VDSO functionality is not
enabled.
This AI slop starts to become annoying.
Thanks,
tglx