From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-drivers-next-2021-12-07
Date: Wed, 08 Dec 2021 10:00:15 +0200 [thread overview]
Message-ID: <87tufjfrw0.fsf@codeaurora.org> (raw)
In-Reply-To: <20211207211412.13c78ace@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (Jakub Kicinski's message of "Tue, 7 Dec 2021 21:14:12 -0800")
Jakub Kicinski <kuba@kernel.org> writes:
> On Tue, 7 Dec 2021 14:42:11 +0000 (UTC) Kalle Valo wrote:
>> here's a pull request to net-next tree, more info below. Please let me know if
>> there are any problems.
>
> Pulled, thanks! Could you chase the appropriate people so that the new
> W=1 C=1 warnings get resolved before the merge window's here?
>
> https://patchwork.kernel.org/project/netdevbpf/patch/20211207144211.A9949C341C1@smtp.kernel.org/
Just so that I understand right, you are referring to this patchwork
test:
Errors and warnings before: 111 this patch: 115
https://patchwork.hopto.org/static/nipa/591659/12662005/build_32bit/
And you want the four new warnings to be fixed? That can be quite time
consuming, to be honest I would rather revert the commits than using a
lot of my time trying to get people fix the warnings. Is there an easy
way to find what are the new warnings?
But in the big picture are you saying the net trees now have a rule that
no new W=1 and C=1 warnings are allowed? I do test ath10k and ath11k
drivers for W=1 and C=1 warnings, but all other drivers are on their own
in this regard. At the moment I have no tooling in place to check all
wireless drivers.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-12-08 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 14:42 pull-request: wireless-drivers-next-2021-12-07 Kalle Valo
2021-12-08 5:14 ` Jakub Kicinski
2021-12-08 8:00 ` Kalle Valo [this message]
2021-12-08 14:50 ` Jakub Kicinski
2021-12-08 15:08 ` Jakub Kicinski
2021-12-08 16:21 ` Kalle Valo
2021-12-08 16:40 ` Kalle Valo
2021-12-08 16:58 ` Loic Poulain
2021-12-16 9:18 ` Kalle Valo
2021-12-19 9:09 ` Luca Coelho
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=87tufjfrw0.fsf@codeaurora.org \
--to=kvalo@kernel.org \
--cc=kuba@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 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 NNTP newsgroup(s).