From: Kalle Valo <kvalo@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ath11k: checking RCU usage
Date: Mon, 22 Jan 2024 16:39:00 +0200 [thread overview]
Message-ID: <87bk9d301n.fsf@kernel.org> (raw)
In-Reply-To: <Za5124pntbOOtURc@hovoldconsulting.com> (Johan Hovold's message of "Mon, 22 Jan 2024 15:04:11 +0100")
Johan Hovold <johan@kernel.org> writes:
> On Mon, Jan 22, 2024 at 02:10:17PM +0100, Johan Hovold wrote:
>> On Sat, Jan 13, 2024 at 12:26:53PM +0200, Kalle Valo wrote:
>
>> > I just found out that sparse has __must_hold():
>> >
>> > https://lore.kernel.org/linux-wireless/87sf31hhfp.fsf@kernel.org/
>> >
>> > That looks promising, should we start using that in ath11k and ath12k to
>> > check our RCU usage?
>>
>> I see that Johannes already commented on this in the thread above.
>>
>> I'm pretty sure smatch can't be used for this.
>
> I meant "sparse"...
Yeah, that was a disappointment. I should have tested it first :)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-01-22 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 15:31 [PATCH v2 0/2] wifi: ath11k: fix event locking Johan Hovold
2023-10-19 15:31 ` [PATCH v2 1/2] wifi: ath11k: fix temperature " Johan Hovold
2023-10-19 17:14 ` Jeff Johnson
2023-10-24 13:59 ` Kalle Valo
2023-10-24 14:29 ` Johan Hovold
2023-10-25 9:51 ` Kalle Valo
2023-10-25 12:26 ` Johan Hovold
2023-10-25 9:59 ` Kalle Valo
2023-10-19 15:31 ` [PATCH v2 2/2] wifi: ath11k: fix dfs radar " Johan Hovold
2023-10-24 14:07 ` [PATCH v2 0/2] wifi: ath11k: fix " Kalle Valo
2023-10-24 15:17 ` Johan Hovold
2024-01-13 10:26 ` ath11k: checking RCU usage Kalle Valo
2024-01-22 13:10 ` Johan Hovold
2024-01-22 14:04 ` Johan Hovold
2024-01-22 14:39 ` Kalle Valo [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=87bk9d301n.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).