From: Waiman Long <llong@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>,
peterz@infradead.org, mingo@kernel.org
Cc: bigeasy@linutronix.de, boqun@kernel.org, will@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] locking/mutex: Fix wrong comment for CONFIG_DEBUG_LOCK_ALLOC
Date: Thu, 19 Feb 2026 08:31:43 -0500 [thread overview]
Message-ID: <64edb58e-b7a5-434b-978f-171301a5c5ab@redhat.com> (raw)
In-Reply-To: <20260217191512.1180151-3-dave@stgolabs.net>
On 2/17/26 2:15 PM, Davidlohr Bueso wrote:
> ... that endif block should be CONFIG_DEBUG_LOCK_ALLOC, not
> CONFIG_LOCKDEP.
>
> Fixes: 51d7a054521d ("locking/mutex: Redo __mutex_init() to reduce generated code size")
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> ---
> include/linux/mutex.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/mutex.h b/include/linux/mutex.h
> index 8126da959088..f57d2a97da57 100644
> --- a/include/linux/mutex.h
> +++ b/include/linux/mutex.h
> @@ -146,7 +146,7 @@ static inline void __mutex_init(struct mutex *lock, const char *name,
> {
> mutex_rt_init_generic(lock);
> }
> -#endif /* !CONFIG_LOCKDEP */
> +#endif /* !CONFIG_DEBUG_LOCK_ALLOC */
> #endif /* CONFIG_PREEMPT_RT */
>
> #ifdef CONFIG_DEBUG_MUTEXES
Reviewed-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2026-02-19 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 19:15 [PATCH -tip 0/3] locking/mutex: Misc fixlets Davidlohr Bueso
2026-02-17 19:15 ` [PATCH 1/3] locking/mutex: Rename mutex_init_lockep() Davidlohr Bueso
2026-02-19 8:32 ` Peter Zijlstra
2026-02-19 13:25 ` Waiman Long
2026-02-23 10:25 ` [tip: locking/core] " tip-bot2 for Davidlohr Bueso
2026-02-17 19:15 ` [PATCH 2/3] locking/mutex: Fix wrong comment for CONFIG_DEBUG_LOCK_ALLOC Davidlohr Bueso
2026-02-19 13:31 ` Waiman Long [this message]
2026-02-23 10:25 ` [tip: locking/core] " tip-bot2 for Davidlohr Bueso
2026-02-17 19:15 ` [PATCH 3/3] locking/mutex: Add killable flavor to guard definitions Davidlohr Bueso
2026-02-23 10:25 ` [tip: locking/core] " tip-bot2 for Davidlohr Bueso
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=64edb58e-b7a5-434b-978f-171301a5c5ab@redhat.com \
--to=llong@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=boqun@kernel.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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®