From: Ingo Molnar <mingo@kernel.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [GIT PULL] [PATCH 0/3] LOCKDEP changes for v6.16
Date: Tue, 6 May 2025 19:23:13 +0200 [thread overview]
Message-ID: <aBpFgSHfpp4-7V_5@gmail.com> (raw)
In-Reply-To: <20250506042049.50060-1-boqun.feng@gmail.com>
* Boqun Feng <boqun.feng@gmail.com> wrote:
> Hi Ingo & Peter,
>
> Please pull the lockdep changes for v6.16 into tip. I'm sending the
> changes in patchset, but I also created a tag and the pull-request
> message in case you want to directly pull. Thanks!
>
> Regards,
> Boqun
>
> The following changes since commit 35e6b537af85d97e0aafd8f2829dfa884a22df20:
>
> lockdep: Remove disable_irq_lockdep() (2025-03-14 21:13:20 +0100)
>
> are available in the Git repository at:
>
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/boqun/linux tags/lockdep-for-tip.2025.05.05
>
> for you to fetch changes up to b3eec4e26ada8a71c40147b45026d2345f3b6ae3:
>
> locking/lockdep: Add # of dynamic keys stat to /proc/lockdep_stats (2025-05-04 11:03:02 -0700)
>
> ----------------------------------------------------------------
> Lockdep changes for v6.16:
>
> - Move hlock_equal() only under CONFIG_LOCKDEP_SMALL=y
> - Prevent abuse of lockdep subclass in __lock_acquire()
> - Add # of dynamic keys stat to /proc/lockdep_stats
>
> ----------------------------------------------------------------
> Andy Shevchenko (1):
> lockdep: Move hlock_equal() to the respective ifdeffery
>
> Waiman Long (2):
> locking/lockdep: Prevent abuse of lockdep subclass
> locking/lockdep: Add # of dynamic keys stat to /proc/lockdep_stats
>
> kernel/locking/lockdep.c | 76 ++++++++++++++++++++------------------
> kernel/locking/lockdep_internals.h | 1 +
> kernel/locking/lockdep_proc.c | 2 +
> 3 files changed, 44 insertions(+), 35 deletions(-)
Thanks, applied to the locking tree (tip:locking/core).
Ingo
prev parent reply other threads:[~2025-05-06 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 4:20 [GIT PULL] [PATCH 0/3] LOCKDEP changes for v6.16 Boqun Feng
2025-05-06 4:20 ` [PATCH 1/3] lockdep: Move hlock_equal() to the respective ifdeffery Boqun Feng
2025-05-06 17:52 ` [tip: locking/core] locking/lockdep: Move hlock_equal() to the respective #ifdeffery tip-bot2 for Andy Shevchenko
2025-05-06 4:20 ` [PATCH 2/3] locking/lockdep: Prevent abuse of lockdep subclass Boqun Feng
2025-05-06 17:52 ` [tip: locking/core] " tip-bot2 for Waiman Long
2025-05-06 4:20 ` [PATCH 3/3] locking/lockdep: Add # of dynamic keys stat to /proc/lockdep_stats Boqun Feng
2025-05-06 17:51 ` [tip: locking/core] locking/lockdep: Add number of dynamic keys " tip-bot2 for Waiman Long
2025-05-06 17:23 ` Ingo Molnar [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=aBpFgSHfpp4-7V_5@gmail.com \
--to=mingo@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.