Ping-Ke Shih <pkshih@xxxxxxxxxxx> 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@xxxxxxxxxx/ 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
