From: Karl Mehltretter <kmehltretter@gmail.com>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>
Cc: "Karl Mehltretter" <kmehltretter@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH] futex: Fix futex_do_wait() reference in kernel-doc
Date: Fri, 11 Sep 2026 23:56:54 +0200 [thread overview]
Message-ID: <20260911215655.6557-1-kmehltretter@gmail.com> (raw)
The kernel-doc comment of futex_wait_requeue_pi() refers to
futex_wait_queue, which was renamed to futex_do_wait by
commit 93f1b6d79a73 ("futex: Move futex_queue() into
futex_wait_setup()"). Say futex_do_wait.
Fixes: 93f1b6d79a73 ("futex: Move futex_queue() into futex_wait_setup()")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
kernel/futex/requeue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/futex/requeue.c b/kernel/futex/requeue.c
index b3f4a4bccb12635f8e621420cb22511ab2c75ad8..6979cee4b69d9ed863bb00583942138227f20720 100644
--- a/kernel/futex/requeue.c
+++ b/kernel/futex/requeue.c
@@ -768,7 +768,7 @@ int handle_early_requeue_pi_wakeup(struct futex_hash_bucket *hb,
* without one, the pi logic would not know which task to boost/deboost, if
* there was a need to.
*
- * We call schedule in futex_wait_queue() when we enqueue and return there
+ * We call schedule in futex_do_wait() when we enqueue and return there
* via the following--
* 1) wakeup on uaddr2 after an atomic lock acquisition by futex_requeue()
* 2) wakeup on uaddr2 after a requeue
next reply other threads:[~2026-09-11 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 21:56 Karl Mehltretter [this message]
2026-09-14 7:21 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260911215655.6557-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®