From: Kalle Valo <kvalo@kernel.org>
To: Arend van Spriel <aspriel@gmail.com>
Cc: <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFH] wireless-next: fix new W=1 warnings
Date: Tue, 17 Oct 2023 18:31:52 +0300 [thread overview]
Message-ID: <87a5sh2rkn.fsf@kernel.org> (raw)
In-Reply-To: <18b3e27d218.279b.9696ff82abe5fb6502268bdc3b0467d4@gmail.com> (Arend van Spriel's message of "Tue, 17 Oct 2023 17:01:19 +0200")
Arend van Spriel <aspriel@gmail.com> writes:
> On October 9, 2023 9:10:11 AM Kalle Valo <kvalo@kernel.org> wrote:
>
>> Hi,
>>
>> During the weekend we updated wireless-next tree from v6.5 to v6.6-rc4+.
>> It looks like a new warning was enabled for v6.6 as I see with GCC 13.2
>> and W=1 several warnings (list below). In v6.5 wireless code was still
>> W=1 warning free with GCC.
>
> Can't say I am a big fan of this new warning, but I will look at the
> brcmfmac related warnings.
I already sent a patch, please take a look:
https://patchwork.kernel.org/project/linux-wireless/patch/20231012135854.3473332-1-kvalo@kernel.org/
> Btw. is it possible to opt out per driver.
Usually that's not preferred.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-10-17 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 7:09 [RFH] wireless-next: fix new W=1 warnings Kalle Valo
2023-10-09 9:07 ` Bagas Sanjaya
2023-10-09 9:07 ` Bagas Sanjaya
2023-10-17 15:01 ` Arend van Spriel
2023-10-17 15:31 ` Kalle Valo [this message]
2023-10-17 15:49 ` [PATCH] wifi: ath9k: fix -Wformat-truncation warning Dmitry Antipov
2023-10-20 14:45 ` Kalle Valo
2023-10-20 15:26 ` Dmitry Antipov
2023-10-17 15:53 ` [PATCH] wifi: ath11k: " Dmitry Antipov
2023-10-17 15:53 ` Dmitry Antipov
2023-10-17 19:38 ` Jeff Johnson
2023-10-17 19:38 ` Jeff Johnson
2023-10-17 16:51 ` [PATCH] wifi: ipw2x00: fix -Wformat-truncation warnings Dmitry Antipov
2023-10-20 14:50 ` Kalle Valo
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=87a5sh2rkn.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=aspriel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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.