From: Stefan Wiehler <stefan.wiehler@nokia.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>,
linux-arm-kernel@lists.infradead.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: smp: Avoid false positive CPU hotplug Lockdep-RCU splat
Date: Mon, 11 Mar 2024 17:17:43 +0100 [thread overview]
Message-ID: <c0001d35-a75a-4cdf-917b-8e1ec159502d@nokia.com> (raw)
In-Reply-To: <Ze8sl01dgGTLcREs@shell.armlinux.org.uk>
> So what do I do about this? I see you submitted this to the patch system
> on the 8th March, but proposed a different approach on the 9th March. I
> don't see evidence that Paul is happy with the original approach either
> and there's no ack/r-b's on anything here.
I think we need to wait for feedback from Will Deacon regarding the new
arch_spin_lock() based approach. So please abandon the original proposal in the
patch system, at least for now…
next prev parent reply other threads:[~2024-03-11 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 16:09 Stefan Wiehler
2024-03-07 17:45 ` Paul E. McKenney
2024-03-07 17:49 ` Paul E. McKenney
2024-03-07 18:54 ` Russell King (Oracle)
2024-03-07 19:08 ` Paul E. McKenney
2024-03-07 18:49 ` Boqun Feng
2024-03-08 10:20 ` Stefan Wiehler
2024-03-08 14:57 ` Joel Fernandes
2024-03-09 7:45 ` Stefan Wiehler
2024-03-09 9:57 ` Russell King (Oracle)
2024-03-12 22:14 ` Will Deacon
2024-03-12 22:39 ` Russell King (Oracle)
2024-03-13 0:32 ` Will Deacon
2024-03-13 9:58 ` Russell King (Oracle)
2024-08-09 13:37 ` Stefan Wiehler
2024-08-09 13:48 ` Russell King (Oracle)
2024-08-09 14:06 ` Stefan Wiehler
2024-03-11 16:08 ` Russell King (Oracle)
2024-03-11 16:17 ` Stefan Wiehler [this message]
2024-03-11 19:01 ` Paul E. McKenney
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=c0001d35-a75a-4cdf-917b-8e1ec159502d@nokia.com \
--to=stefan.wiehler@nokia.com \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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®