From 7006cb82bde1dbcd9465186fd31aa884e679f92c Mon Sep 17 00:00:00 2001 From: Andreas Kling Date: Mon, 23 Aug 2021 02:09:08 +0200 Subject: Kernel: Rename Blocker::not_blocking(bool) to something more descriptive Namely, will_unblock_immediately_without_blocking(Reason). This virtual function is called on a blocker *before any block occurs*, if it turns out that we don't need to block the thread after all. This can happens for one of two reasons: - UnblockImmediatelyReason::UnblockConditionAlreadyMet We don't need to block the thread because the condition for unblocking it is already met. - UnblockImmediatelyReason::TimeoutInThePast We don't need to block the thread because a timeout was specified and that timeout is already in the past. This patch does not introduce any behavior changes, it's only meant to clarify this part of the blocking logic. --- Kernel/FileSystem/Plan9FileSystem.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Kernel/FileSystem/Plan9FileSystem.h') diff --git a/Kernel/FileSystem/Plan9FileSystem.h b/Kernel/FileSystem/Plan9FileSystem.h index 30788b5d06..36148d536f 100644 --- a/Kernel/FileSystem/Plan9FileSystem.h +++ b/Kernel/FileSystem/Plan9FileSystem.h @@ -91,7 +91,7 @@ private: } virtual StringView state_string() const override { return "Waiting"sv; } virtual Type blocker_type() const override { return Type::Plan9FS; } - virtual void not_blocking(bool) override; + virtual void will_unblock_immediately_without_blocking(UnblockImmediatelyReason) override; const NonnullRefPtr& completion() const { return m_completion; } u16 tag() const { return m_completion->tag; } -- cgit v1.2.3