Received-SPF: pass (google.com: domain of linux-wireless+bounces-3551-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
  "johannes.berg@intel.com" <johannes.berg@intel.com>
Subject: Re: [PATCH] wifi: rtw89: fw: remove unnecessary rcu_read_unlock()
 for punctured
References: <20240213122556.9593-1-pkshih@realtek.com>
	<87ttmced8l.fsf@kernel.org>
	<f8b28bf1f735432489c1674d62fc68a8cf475ee8.camel@realtek.com>
Date: Tue, 13 Feb 2024 17:22:56 +0200
In-Reply-To: <f8b28bf1f735432489c1674d62fc68a8cf475ee8.camel@realtek.com>
	(Ping-Ke Shih's message of "Tue, 13 Feb 2024 13:43:46 +0000")
Message-ID: <874jecpewf.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

Ping-Ke Shih <pkshih@realtek.com> writes:

>> This again shows how important it is to fix all the remainging sparse
>> warnings in wireless code so that we don't miss important warnings like
>> this. If there just would be a way to get the cleanup patch submitters
>> to fix the sparse warnings, sigh.
>
> In short term, can we record the count of warnings and ensure it
> doesn't increase while new commits are getting merged? 

Netdev has that kind of checks in checkpatch:

netdev/build_allmodconfig_warn	success	Errors and warnings before: 993 this patch: 992

https://patchwork.kernel.org/project/netdevbpf/patch/20240213112122.404045-2-leitao@debian.org/

But in wireless project we have not set up that. That reminds me that I
need to reply to Jakub's email related to this.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches