From: Carlos Llamas <cmllamas@google.com>
To: "zhangxiaomeng (A)" <zhangxiaomeng13@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
"J. R. Okajima" <hooanon05g@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Waiman Long <longman@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>
Subject: Re: 回复: [PATCH] lockdep: Fix upper limit for LOCKDEP_BITS configs
Date: Thu, 20 Mar 2025 16:11:29 +0000 [thread overview]
Message-ID: <Z9w-MVjD4olLlKDa@google.com> (raw)
In-Reply-To: <629305cc0e6b433d90354fb22d3bacf1@huawei.com>
On Wed, Mar 19, 2025 at 09:48:11AM +0000, zhangxiaomeng (A) wrote:
> Thank you for the response. I should clarify that the issue occurs when modifying additional config values. Specifically, when LOCKDEP_BITS is set to 24 along with setting LOCKDEP_CHAINS_BITS and LOCKDEP_STACK_TRACE_BITS to their maximum upper limits, the build fails.
Right, that's what I figured. I don't know that bumping all these values
to their limit at once makes sense. I think allowing LOCKDEP_BITS to go
higher independently might still be useful so I don't see a reason to
change that.
--
Carlos Llamas
prev parent reply other threads:[~2025-03-20 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 6:47 [PATCH] lockdep: Fix upper limit for LOCKDEP_BITS configs Xiaomeng Zhang
2025-03-14 14:08 ` Waiman Long
2025-03-14 18:33 ` Carlos Llamas
2025-03-19 9:48 ` 回复: " zhangxiaomeng (A)
2025-03-20 16:11 ` Carlos Llamas [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=Z9w-MVjD4olLlKDa@google.com \
--to=cmllamas@google.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=hooanon05g@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=zhangxiaomeng13@huawei.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