From: Johannes Berg <johannes@sipsolutions.net>
To: Aloka Dixit <quic_alokad@quicinc.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 5/6] wifi: cfg80211: add puncturing bitmap in channel switch notifications
Date: Mon, 30 Jan 2023 09:45:29 +0100 [thread overview]
Message-ID: <91f8553f190069da19c907c1819f8ae5c40ceb17.camel@sipsolutions.net> (raw)
In-Reply-To: <20230130072239.26345-6-quic_alokad@quicinc.com>
On Sun, 2023-01-29 at 23:22 -0800, Aloka Dixit wrote:
>
> + * @punct_bitmap: the new puncturing bitmap
> *
> * Caller must acquire wdev_lock, therefore must only be called from sleepable
> * driver context!
> */
> void cfg80211_ch_switch_notify(struct net_device *dev,
> struct cfg80211_chan_def *chandef,
> - unsigned int link_id);
> + unsigned int link_id, u32 punct_bitmap);
Same here: u32 -> u16 since that's sufficient
Maybe we can keep it u32 in the trace, not sure that matters.
johannes
next prev parent reply other threads:[~2023-01-30 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 7:22 [PATCH v3 0/6] Puncturing support in AP mode Aloka Dixit
2023-01-30 7:22 ` [PATCH v3 1/6] wifi: nl80211: configure puncturing bitmap in NL80211_CMD_START_AP Aloka Dixit
2023-01-30 8:40 ` Johannes Berg
2023-01-30 19:35 ` Aloka Dixit
2023-01-30 19:40 ` Aloka Dixit
2023-01-30 7:22 ` [PATCH v3 2/6] wifi: mac80211: validate and configure puncturing bitmap in start_ap() Aloka Dixit
2023-01-30 8:42 ` Johannes Berg
2023-01-30 7:22 ` [PATCH v3 3/6] wifi: nl80211: configure puncturing in NL80211_CMD_CHANNEL_SWITCH Aloka Dixit
2023-01-30 8:43 ` Johannes Berg
2023-01-30 7:22 ` [PATCH v3 4/6] wifi: mac80211: configure puncturing bitmap in channel_switch() Aloka Dixit
2023-01-30 8:44 ` Johannes Berg
2023-01-30 7:22 ` [PATCH v3 5/6] wifi: cfg80211: add puncturing bitmap in channel switch notifications Aloka Dixit
2023-01-30 8:45 ` Johannes Berg [this message]
2023-01-30 7:22 ` [PATCH v3 6/6] wifi: nl80211: add puncturing bitmap in channel switch events Aloka Dixit
2023-01-30 8:48 ` [PATCH v3 0/6] Puncturing support in AP mode Johannes Berg
2023-01-30 19:44 ` Aloka Dixit
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=91f8553f190069da19c907c1819f8ae5c40ceb17.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.com \
/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.