From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, Borislav Petkov <bp@alien8.de>,
Uros Bizjak <ubizjak@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [GIT PULL] locking changes for v6.17
Date: Tue, 29 Jul 2025 08:52:04 +0200 [thread overview]
Message-ID: <aIhvlNUoN5KyPzg6@gmail.com> (raw)
Linus,
Please pull the latest locking/core Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2025-07-29
# HEAD: ba28549bad8ab2b09264ebc8c2ca24af3537ee52 Merge tag 'lockdep-for-tip.2025.07.16' of git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux into locking/core
Locking updates for v6.16:
Locking primitives:
- Mark devm_mutex_init() as __must_check and fix drivers
that didn't check the return code. (Thomas Weißschuh)
- Reorganize <linux/local_lock.h> to better expose the
internal APIs to local variables. (Sebastian Andrzej Siewior)
- Remove OWNER_SPINNABLE in rwsem (Jinliang Zheng)
- Remove redundant #ifdefs in the mutex code (Ran Xiaokai)
Lockdep:
- Avoid returning struct in lock_stats() (Arnd Bergmann)
- Change `static const` into enum for LOCKF_*_IRQ_*
(Arnd Bergmann)
- Temporarily use synchronize_rcu_expedited() in
lockdep_unregister_key() to speed things up.
(Breno Leitao)
Rust runtime:
- Add #[must_use] to Lock::try_lock() (Jason Devers)
Thanks,
Ingo
------------------>
Arnd Bergmann (2):
locking/lockdep: Avoid struct return in lock_stats()
locking/lockdep: Change 'static const' variables to enum values
Breno Leitao (1):
lockdep: Speed up lockdep_unregister_key() with expedited RCU synchronization
Jason Devers (1):
rust: sync: Add #[must_use] to Lock::try_lock()
Jinliang Zheng (1):
locking/rwsem: Use OWNER_NONSPINNABLE directly instead of OWNER_SPINNABLE
Ran Xiaokai (1):
locking/mutex: Remove redundant #ifdefs
Sebastian Andrzej Siewior (1):
local_lock: Move this_cpu_ptr() notation from internal to main header
Thomas Weißschuh (3):
spi: spi-nxp-fspi: Check return value of devm_mutex_init()
leds: lp8860: Check return value of devm_mutex_init()
locking/mutex: Mark devm_mutex_init() as __must_check
drivers/leds/leds-lp8860.c | 4 +++-
drivers/spi/spi-nxp-fspi.c | 4 +++-
include/linux/local_lock.h | 20 +++++++++----------
include/linux/local_lock_internal.h | 30 ++++++++++++++--------------
include/linux/lockdep_types.h | 2 +-
include/linux/mutex.h | 11 +++++++----
kernel/locking/lockdep.c | 39 +++++++++++++++++++++----------------
kernel/locking/lockdep_internals.h | 18 +++++++++--------
kernel/locking/lockdep_proc.c | 2 +-
kernel/locking/mutex.c | 4 ----
kernel/locking/rwsem.c | 4 +---
rust/kernel/sync/lock.rs | 2 ++
12 files changed, 75 insertions(+), 65 deletions(-)
next reply other threads:[~2025-07-29 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 6:52 Ingo Molnar [this message]
2025-07-30 3:39 ` pr-tracker-bot
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=aIhvlNUoN5KyPzg6@gmail.com \
--to=mingo@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--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®