From: Kalle Valo <kvalo@kernel.org>
To: Muna Sinada <quic_msinada@quicinc.com>
Cc: <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>,
Aloka Dixit <quic_alokad@quicinc.com>
Subject: Re: [RFC 1/4] wifi: nl80211: advertise RU puncturing support to userspace
Date: Wed, 14 Dec 2022 10:02:18 +0200 [thread overview]
Message-ID: <87tu1yl8fp.fsf@kernel.org> (raw)
In-Reply-To: <1670006154-6092-2-git-send-email-quic_msinada@quicinc.com> (Muna Sinada's message of "Fri, 2 Dec 2022 10:35:51 -0800")
Muna Sinada <quic_msinada@quicinc.com> writes:
> From: Aloka Dixit <quic_alokad@quicinc.com>
>
> RU preamble puncturing is allowed for bandwidths more than 80 MHz
> except 80+80. Drivers may not support puncturing at all or have
> restrictions for a minimum bandwidth.
> Add new attribute NL80211_ATTR_RU_PUNCT_SUPP_BW to advertise the
> driver support to the userspace. Default value (0) will indicate that
> RU puncturing is not supported.
>
> Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
Missing submitter's s-o-b.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-12-14 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:35 [RFC 0/4] Static RU Puncturing Muna Sinada
2022-12-02 18:35 ` [RFC 1/4] wifi: nl80211: advertise RU puncturing support to userspace Muna Sinada
2022-12-14 8:02 ` Kalle Valo [this message]
2023-01-19 15:31 ` Johannes Berg
2022-12-02 18:35 ` [RFC 2/4] wifi: cfg80211: RU puncturing bitmap Muna Sinada
2023-01-19 15:34 ` Johannes Berg
2022-12-02 18:35 ` [RFC 3/4] wifi: nl80211: validate " Muna Sinada
2023-01-19 15:37 ` Johannes Berg
2023-01-20 0:42 ` Aloka Dixit
2023-01-20 9:20 ` Johannes Berg
2023-01-23 18:28 ` Aloka Dixit
2022-12-02 18:35 ` [RFC 4/4] wifi: mac80211: Handle RU Puncturing information Muna Sinada
2023-01-19 15:40 ` Johannes Berg
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=87tu1yl8fp.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.com \
--cc=quic_msinada@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.