From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
tglx@linutronix.de, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v3 RESEND 0/2] locking/local_lock: shadowing and maintainers entry
Date: Fri, 28 Nov 2025 11:04:51 +0100 [thread overview]
Message-ID: <20251128100451.GX4067720@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251127144140.215722-1-bigeasy@linutronix.de>
On Thu, Nov 27, 2025 at 03:41:38PM +0100, Sebastian Andrzej Siewior wrote:
> This is a repost of two individual postings earlier:
> https://lore.kernel.org/all/20250927090110.t8Tm9yrk@linutronix.de/
> https://lore.kernel.org/all/20251009103900.2Fk8stnM@linutronix.de/
>
> Sebastian Andrzej Siewior (1):
> locking: Add local_locks to MAINTAINERS
>
> Vincent Mailhol (1):
> locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce risk of
> shadowing
>
> MAINTAINERS | 1 +
> include/linux/local_lock_internal.h | 62 ++++++++++++++---------------
> 2 files changed, 32 insertions(+), 31 deletions(-)
Thanks, stuck in queue/locking/core.
prev parent reply other threads:[~2025-11-28 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 14:41 Sebastian Andrzej Siewior
2025-11-27 14:41 ` [PATCH 1/2] locking: Add local_locks to MAINTAINERS Sebastian Andrzej Siewior
2025-11-29 11:49 ` [tip: locking/core] " 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 ` Peter Zijlstra [this message]
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=20251128100451.GX4067720@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=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=tglx@linutronix.de \
--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®