From: Peter Zijlstra <peterz@infradead.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>,
linux-xtensa@linux-xtensa.org,
Johannes Berg <johannes@sipsolutions.net>,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-um@lists.infradead.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v2] LOCKDEP: reduce LOCKDEP dependency list
Date: Tue, 25 May 2021 09:08:20 +0200 [thread overview]
Message-ID: <YKyiZBAGcbGMEjTc@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <3398848.TK9RqziN78@ubuntu-mate-laptop>
On Mon, May 24, 2021 at 11:31:22PM -0400, Julian Braha wrote:
> Hi Randy,
>
> It seems I introduced a new unmet dependency bug
> in my attempt to fix one :/
>
> Anyway, I don't see why the dependency on FRAME_POINTER
> was necessary in the first place, so LGTM.
It might have been an attempt at ensuring sane backtraces; but I didn't
dig into the history of the thing. Either way around, it's fairly
out-dated if that was indeed the case.
next prev parent reply other threads:[~2021-05-25 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 22:41 [PATCH v2] LOCKDEP: reduce LOCKDEP dependency list Randy Dunlap
2021-05-25 3:31 ` Julian Braha
2021-05-25 7:08 ` Peter Zijlstra [this message]
2021-05-25 7:07 ` Peter Zijlstra
2021-05-25 14:17 ` Waiman Long
2021-05-31 10:40 ` [tip: locking/core] locking/lockdep: Reduce " tip-bot2 for Randy Dunlap
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=YKyiZBAGcbGMEjTc@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=boqun.feng@gmail.com \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=jdike@addtoit.com \
--cc=johannes@sipsolutions.net \
--cc=julianbraha@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--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;
as well as URLs for NNTP newsgroup(s).