From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
George Stark <gnstark@salutedevices.com>,
Waiman Long <longman@redhat.com>
Subject: [PATCH v2 0/4] locking: Some locking code cleanups
Date: Thu, 22 Feb 2024 10:05:36 -0500 [thread overview]
Message-ID: <20240222150540.79981-1-longman@redhat.com> (raw)
v2:
- Add Boqun's "Reviewed-by" tags & twist the mutex patch as suggested
by him.
This series contains a number of cleanup locking patches.
Waiman Long (4):
locking/qspinlock: Fix 'wait_early' set but not used warning
locking/mutex: Clean up mutex.h
locking/rwsem: Clarify that RWSEM_READER_OWNED is just a hint
locking/rwsem: Make DEBUG_RWSEMS and PREEMPT_RT mutually exclusive
include/linux/mutex.h | 8 ++------
kernel/locking/qspinlock_paravirt.h | 2 +-
kernel/locking/rwsem.c | 6 +++---
lib/Kconfig.debug | 4 ++--
4 files changed, 8 insertions(+), 12 deletions(-)
--
2.39.3
next reply other threads:[~2024-02-22 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:05 Waiman Long [this message]
2024-02-22 15:05 ` [PATCH v2 1/4] locking/qspinlock: Fix 'wait_early' set but not used warning Waiman Long
2024-02-28 12:53 ` [tip: locking/core] " tip-bot2 for Waiman Long
2024-03-11 10:57 ` Ingo Molnar
2024-03-11 13:45 ` Waiman Long
2024-02-22 15:05 ` [PATCH v2 2/4] locking/mutex: Clean up mutex.h Waiman Long
2024-02-28 12:53 ` [tip: locking/core] locking/mutex: Simplify <linux/mutex.h> tip-bot2 for Waiman Long
2024-02-22 15:05 ` [PATCH v2 3/4] locking/rwsem: Clarify that RWSEM_READER_OWNED is just a hint Waiman Long
2024-02-28 12:53 ` [tip: locking/core] " tip-bot2 for Waiman Long
2024-02-22 15:05 ` [PATCH v2 4/4] locking/rwsem: Make DEBUG_RWSEMS and PREEMPT_RT mutually exclusive Waiman Long
2024-02-28 12:53 ` [tip: locking/core] " tip-bot2 for Waiman Long
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=20240222150540.79981-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=gnstark@salutedevices.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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