All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: kvalo@kernel.org, johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/8] Fix/silence GCC 12 warnings in drivers/net/wireless/
Date: Fri, 20 May 2022 12:43:12 -0700	[thread overview]
Message-ID: <20220520194320.2356236-1-kuba@kernel.org> (raw)

Hi Kalle & Johannes,

as mentioned off list we'd like to get GCC 12 warnings quashed.
This set takes care of the warnings we have in drivers/net/wireless/
mostly by relegating them to W=1/W=2 builds.

Is it okay for us to take this directly to net-next?
Or perhaps via wireless-next with a quick PR by Monday?

Jakub Kicinski (8):
  wifi: plfxlc: remove redundant NULL-check for GCC 12
  wifi: ath9k: silence array-bounds warning on GCC 12
  wifi: rtlwifi: remove always-true condition pointed out by GCC 12
  wifi: ath6k: silence false positive -Wno-dangling-pointer warning on
    GCC 12
  wifi: iwlwifi: use unsigned to silence a GCC 12 warning
  wifi: brcmfmac: work around a GCC 12 -Warray-bounds warning
  wifi: libertas: silence a GCC 12 -Warray-bounds warning
  wifi: carl9170: silence a GCC 12 -Warray-bounds warning

 drivers/net/wireless/ath/ath6kl/Makefile                    | 5 +++++
 drivers/net/wireless/ath/ath9k/Makefile                     | 5 +++++
 drivers/net/wireless/ath/carl9170/Makefile                  | 5 +++++
 drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 +-
 drivers/net/wireless/intel/iwlwifi/mvm/sta.c                | 2 +-
 drivers/net/wireless/marvell/libertas/Makefile              | 5 +++++
 drivers/net/wireless/purelifi/plfxlc/usb.c                  | 4 ++--
 drivers/net/wireless/realtek/rtlwifi/rtl8192de/phy.c        | 5 +----
 8 files changed, 25 insertions(+), 8 deletions(-)

-- 
2.34.3


             reply	other threads:[~2022-05-20 19:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 19:43 Jakub Kicinski [this message]
2022-05-20 19:43 ` [PATCH net-next 1/8] wifi: plfxlc: remove redundant NULL-check for GCC 12 Jakub Kicinski
2022-05-20 19:43 ` [PATCH net-next 2/8] wifi: ath9k: silence array-bounds warning on " Jakub Kicinski
2022-05-21  6:58   ` Kalle Valo
2022-05-21 17:53     ` Jakub Kicinski
2022-05-22 12:06       ` Kalle Valo
2022-05-23 19:31     ` Kees Cook
2022-05-20 19:43 ` [PATCH net-next 3/8] wifi: rtlwifi: remove always-true condition pointed out by " Jakub Kicinski
2022-05-23  2:35   ` Ping-Ke Shih
2022-05-23 15:57     ` Jakub Kicinski
2022-05-24  0:41       ` Ping-Ke Shih
2022-05-20 19:43 ` [PATCH net-next 4/8] wifi: ath6k: silence false positive -Wno-dangling-pointer warning on " Jakub Kicinski
2022-05-20 19:43 ` [PATCH net-next 5/8] wifi: iwlwifi: use unsigned to silence a GCC 12 warning Jakub Kicinski
2022-05-20 19:43 ` [PATCH net-next 6/8] wifi: brcmfmac: work around a GCC 12 -Warray-bounds warning Jakub Kicinski
2022-05-20 19:43 ` [PATCH net-next 7/8] wifi: libertas: silence " Jakub Kicinski
2022-05-21 22:03   ` Johannes Berg
2022-05-22 16:56     ` Jakub Kicinski
2022-05-20 19:43 ` [PATCH net-next 8/8] wifi: carl9170: " Jakub Kicinski
2022-05-20 19:58   ` Christian Lamparter
2022-05-22 12:19 ` [PATCH net-next 0/8] Fix/silence GCC 12 warnings in drivers/net/wireless/ 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=20220520194320.2356236-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=johannes@sipsolutions.net \
    --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.