mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Carlos Llamas <cmllamas@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel-team@android.com,
	Huang Ying <ying.huang@intel.com>,
	"J. R. Okajima" <hooanon05g@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Waiman Long <longman@redhat.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v3 0/3] lockdep: minor config and documentation fixes
Date: Mon, 28 Oct 2024 10:34:56 -0700	[thread overview]
Message-ID: <Zx_LQN1pgp6f9wM5@Boquns-Mac-mini.local> (raw)
In-Reply-To: <20241024183631.643450-1-cmllamas@google.com>

On Thu, Oct 24, 2024 at 06:36:25PM +0000, Carlos Llamas wrote:
> These are some minor follow-up patches that came up during conversation
> at: https://lore.kernel.org/all/30795.1620913191@jrobl/
> 
> This v3 is based on master as commit e0ba72e3a442 ("lockdep: upper limit
> LOCKDEP_CHAINS_BITS") has now landed.
> 
> Cc: Huang Ying <ying.huang@intel.com>
> Cc: J. R. Okajima <hooanon05g@gmail.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Waiman Long <longman@redhat.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> 

Queued into lockdep-for-tip for future tests and reviews, if all goes
well, this will be merged in tip during v6.13 and in mainline during
v6.14 merge window.

Thanks!

Regards,
Boqun

> v3: rebased on master and collected tags
> v2: https://lore.kernel.org/all/20240807143922.919604-1-cmllamas@google.com/
> v1: https://lore.kernel.org/all/20240806010128.402852-1-cmllamas@google.com/
> 
> Carlos Llamas (3):
>   lockdep: fix upper limit for LOCKDEP_*_BITS configs
>   lockdep: clarify size for LOCKDEP_*_BITS configs
>   lockdep: document MAX_LOCKDEP_CHAIN_HLOCKS calculation
> 
>  kernel/locking/lockdep_internals.h |  3 ++-
>  lib/Kconfig.debug                  | 18 +++++++++---------
>  2 files changed, 11 insertions(+), 10 deletions(-)
> 
> -- 
> 2.47.0.163.g1226f6d8fa-goog
> 

      parent reply	other threads:[~2024-10-28 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 18:36 Carlos Llamas
2024-10-24 18:36 ` [PATCH v3 1/3] lockdep: fix upper limit for LOCKDEP_*_BITS configs Carlos Llamas
2024-12-24 18:53   ` [tip: locking/core] lockdep: Fix " tip-bot2 for Carlos Llamas
2024-10-24 18:36 ` [PATCH v3 2/3] lockdep: clarify size " Carlos Llamas
2024-10-24 19:00   ` Waiman Long
2024-12-24 18:53   ` [tip: locking/core] lockdep: Clarify " tip-bot2 for Carlos Llamas
2024-10-24 18:36 ` [PATCH v3 3/3] lockdep: document MAX_LOCKDEP_CHAIN_HLOCKS calculation Carlos Llamas
2024-10-24 19:01   ` Waiman Long
2024-10-25  3:01   ` Huang, Ying
2024-12-24 18:53   ` [tip: locking/core] lockdep: Document " tip-bot2 for Carlos Llamas
2024-10-28 17:34 ` Boqun Feng [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=Zx_LQN1pgp6f9wM5@Boquns-Mac-mini.local \
    --to=boqun.feng@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cmllamas@google.com \
    --cc=hooanon05g@gmail.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will@kernel.org \
    --cc=ying.huang@intel.com \
    /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®