From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Arend Van Spriel <arend.vanspriel@broadcom.com>,
<netdev@vger.kernel.org>, <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: wireless-next-2024-01-25
Date: Fri, 26 Jan 2024 10:52:55 -0800 [thread overview]
Message-ID: <20240126105255.5476cf85@kernel.org> (raw)
In-Reply-To: <877cjwz9ya.fsf@kernel.org>
On Fri, 26 Jan 2024 12:05:17 +0200 Kalle Valo wrote:
> > I thought checkpatch would signal that or is it a sparse warning.
>
> I don't run checkpatch except for ath10k/ath11k/ath12k, too much noise.
> I ended up adding this to my script:
We run build with sparse and W=1 and then diff the number of warnings
to weed out the pre-existing ones, FWIW.
next prev parent reply other threads:[~2024-01-26 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 10:40 pull-request: wireless-next-2024-01-25 Kalle Valo
2024-01-26 0:51 ` Jakub Kicinski
2024-01-26 6:01 ` Kalle Valo
2024-01-26 6:37 ` Arend Van Spriel
2024-01-26 10:05 ` Kalle Valo
2024-01-26 18:52 ` Jakub Kicinski [this message]
2024-01-27 10:08 ` Kalle Valo
2024-01-29 19:55 ` Jakub Kicinski
2024-02-13 15:27 ` Kalle Valo
2024-01-26 1:10 ` patchwork-bot+netdevbpf
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=20240126105255.5476cf85@kernel.org \
--to=kuba@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.