From: Johannes Berg <johannes@sipsolutions.net>
To: Pablo Martin-Gomez <pmartin-gomez@freebox.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 2/7] wifi: make EHT capa size check not read reserved bits
Date: Fri, 10 Apr 2026 22:35:07 +0200 [thread overview]
Message-ID: <2d8d1edeeefb720acfdfcc595a7fca615ae64a64.camel@sipsolutions.net> (raw)
In-Reply-To: <20260410190354.394742-3-pmartin-gomez@freebox.fr> (sfid-20260410_210402_706482_E2BE5CC8)
On Fri, 2026-04-10 at 21:03 +0200, Pablo Martin-Gomez wrote:
>
> drivers/net/wireless/ath/ath12k/mac.c | 3 +-
> include/linux/ieee80211-eht.h | 58 ++++++++++++++++-----------
> net/mac80211/eht.c | 3 +-
> net/mac80211/util.c | 8 ++--
> net/wireless/nl80211.c | 13 ++++--
>
> static inline bool
> ieee80211_eht_capa_size_ok(const u8 *he_capa, const u8 *data, u8 len,
> - bool from_ap)
> + bool from_ap, enum nl80211_band band)
I don't see how this can build without adjusting net/mac80211/parse.c?
johannes
next prev parent reply other threads:[~2026-04-10 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 19:03 [RFC PATCH 0/7] Do not read band-dependent reserved bits Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 1/7] wifi: nl80211: remove EHT IE size validation Pablo Martin-Gomez
2026-04-10 20:25 ` Johannes Berg
2026-04-10 19:03 ` [RFC PATCH 2/7] wifi: make EHT capa size check not read reserved bits Pablo Martin-Gomez
2026-04-10 20:35 ` Johannes Berg [this message]
2026-04-10 19:03 ` [RFC PATCH 3/7] wifi: make HE " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 4/7] wifi: do not read band-dependent " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 5/7] wifi: ath11k: " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 6/7] wifi: ath12k: " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 7/7] wifi: mt76: " Pablo Martin-Gomez
2026-04-15 22:38 ` [RFC PATCH 0/7] Do " Jeff Johnson
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=2d8d1edeeefb720acfdfcc595a7fca615ae64a64.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pmartin-gomez@freebox.fr \
/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