From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Cc: tglx@linutronix.de, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>
Subject: [PATCH 1/2] locking: Add local_locks to MAINTAINERS
Date: Thu, 27 Nov 2025 15:41:39 +0100 [thread overview]
Message-ID: <20251127144140.215722-2-bigeasy@linutronix.de> (raw)
In-Reply-To: <20251127144140.215722-1-bigeasy@linutronix.de>
The local_lock_t was never added to the MAINTAINERS file since its
inclusion.
Add local_lock_t to the locking primitives section.
Cc: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Waiman Long <longman@redhat.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6df89b14b521a..6939d27bc1f2d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14535,6 +14535,7 @@ S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
F: Documentation/locking/
F: arch/*/include/asm/spinlock*.h
+F: include/linux/local_lock*.h
F: include/linux/lockdep*.h
F: include/linux/mutex*.h
F: include/linux/rwlock*.h
--
2.51.0
next prev parent reply other threads:[~2025-11-27 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 14:41 [PATCH v3 RESEND 0/2] locking/local_lock: shadowing and maintainers entry Sebastian Andrzej Siewior
2025-11-27 14:41 ` Sebastian Andrzej Siewior [this message]
2025-11-29 11:49 ` [tip: locking/core] locking: Add local_locks to MAINTAINERS tip-bot2 for Sebastian Andrzej Siewior
2025-12-01 6:01 ` [tip: locking/core] locking/local_lock: Add the <linux/local_lock*.h> headers " tip-bot2 for Sebastian Andrzej Siewior
2025-11-27 14:41 ` [PATCH 2/2] locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce risk of shadowing Sebastian Andrzej Siewior
2025-11-29 11:49 ` [tip: locking/core] " tip-bot2 for Vincent Mailhol
2025-12-01 6:01 ` [tip: locking/core] locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce the " tip-bot2 for Vincent Mailhol
2025-11-28 10:04 ` [PATCH v3 RESEND 0/2] locking/local_lock: shadowing and maintainers entry Peter Zijlstra
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=20251127144140.215722-2-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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®