From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C6222216E24 for ; Wed, 11 Feb 2026 13:10:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770815409; cv=none; b=kPUOS6t7kh8SCYuoog7AINcEZXugRVzaCKW96UiEPlG6B6+nIeBjKEkCseAFjR7PQG+d8PJQuMFpM2i6AU+PjDjkl2vtCu7JGwdcgppIzqpyzspV46gj3ZtD0my9L3gFtD2R+LQIKmjGJoHYrsLkw1egwtqQFbF/UeqXpazj98Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770815409; c=relaxed/simple; bh=vdT76KLGvrp8shkNUJy43nIXRPBRcUl+1Mtr+oEmnF0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=bHb9VeceeEjxSNqkOuKt1FNQMbC+IMs0Cj+H7Lsrl1nxCqiW4f3L7VX7dIy2K7to1P0S5LNkhgLWBqTuKNfYNbceyEWfyi6HCffGJdhsIyfFAPVxNfN9JIAqPBK1gKuYHiuGzvZgc+NMkC6MKCu+zD12bvwNMm5UULxIqqfP1RY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=o6ZOSZqG; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="o6ZOSZqG" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7567DC4CEF7; Wed, 11 Feb 2026 13:10:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770815408; bh=vdT76KLGvrp8shkNUJy43nIXRPBRcUl+1Mtr+oEmnF0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=o6ZOSZqG2X0lLeKSaGzzTa1gKTZ2CQPOPBhPlinSq8f/ifqeFMzv4VrFyj/xpgN/W DaNdyBFla90FIVLJpE4VdyFywB9kTLlZXnCmwX+5MkL9OmjDygyPEnPEO+f+xqQuID 0mO6ZCmdHL03ec+jUsoQKRIus/C2lXNkK9yiVQF4UfXQg24EkNi61Ize9Whxuo1bU2 pqrRmLiOpbqgEnITTdOrIXlFY+/h2Q3ESW3oKr3j+LbmEf0tOoKvlINXfA0IkOs5FX HVtBhz1f8FsZNwJoW8fyyFOR3/Nownx11EDvyZ/l+QmHF9X2J/c6urU5/Of5SqJDlv EAjCy+X+Xe7lw== From: Thomas Gleixner To: Zhan Xusheng Cc: linux-kernel@vger.kernel.org, Zhan Xusheng Subject: Re: [PATCH] clocksource: Update registration failure behavior documentation In-Reply-To: <20260210025603.143764-1-zhanxusheng@xiaomi.com> References: <20260210025603.143764-1-zhanxusheng@xiaomi.com> Date: Wed, 11 Feb 2026 14:10:05 +0100 Message-ID: <87v7g38lzm.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain 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