From: Davidlohr Bueso <dave@stgolabs.net>
To: peterz@infradead.org, mingo@kernel.org
Cc: bigeasy@linutronix.de, longman@redhat.com, boqun@kernel.org,
will@kernel.org, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dave@stgolabs.net>
Subject: [PATCH -tip 0/3] locking/mutex: Misc fixlets
Date: Tue, 17 Feb 2026 11:15:09 -0800 [thread overview]
Message-ID: <20260217191512.1180151-1-dave@stgolabs.net> (raw)
Found while eyeballing recent changes to mutex.c. The first two are fixes for
51d7a054521d ("locking/mutex: Redo __mutex_init() to reduce generated code size").
Thanks!
Davidlohr Bueso (3):
locking/mutex: Rename mutex_init_lockep()
locking/mutex: Fix wrong comment for CONFIG_DEBUG_LOCK_ALLOC
locking/mutex: Add killable flavor to guard definitions
include/linux/mutex.h | 9 ++++++---
kernel/locking/mutex.c | 4 ++--
2 files changed, 8 insertions(+), 5 deletions(-)
--
2.39.5
next reply other threads:[~2026-02-17 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 19:15 Davidlohr Bueso [this message]
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
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=20260217191512.1180151-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=bigeasy@linutronix.de \
--cc=boqun@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--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®