From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Yu-Hsiang Tseng <asas1asas200@gmail.com>
Cc: Jeff Johnson <jjohnson@kernel.org>,
ath12k@lists.infradead.org,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>,
Kalle Valo <kvalo@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v3] wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions
Date: Thu, 23 Apr 2026 08:30:20 +0200 [thread overview]
Message-ID: <20260423063020.NAero6Rz@linutronix.de> (raw)
In-Reply-To: <20260422180814.1938317-1-asas1asas200@gmail.com>
On 2026-04-23 02:08:14 [+0800], Yu-Hsiang Tseng wrote:
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3
This could written in plain english as in "Tested on …". Not sure what
this "convention" is but anyway.
The change is okay.
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Changes in v3:
> - Use lockdep_assert_in_rcu_read_lock() instead of RCU_LOCKDEP_WARN()
> for clearer intent and more precise semantics (suggested by
> Sebastian Andrzej Siewior)
> - Reword commit message: this affects preemptible RCU in general,
> not only PREEMPT_RT
> - Move Tested-on before the official tags per ath convention
Sebastian
next prev parent reply other threads:[~2026-04-23 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 18:08 [PATCH v3] wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions Yu-Hsiang Tseng
2026-04-23 6:30 ` Sebastian Andrzej Siewior [this message]
2026-04-23 15:24 ` Jeff Johnson
2026-04-23 16:14 ` Sebastian Andrzej Siewior
2026-04-23 18:01 ` Jeff Johnson
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=20260423063020.NAero6Rz@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=asas1asas200@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=clrkwllms@kernel.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=rameshkumar.sundaram@oss.qualcomm.com \
--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