From: Ryder Lee <Ryder.Lee@mediatek.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>
Cc: "Shayne Chen (陳軒丞)" <Shayne.Chen@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Evelyn Tsai (蔡珊鈺)" <Evelyn.Tsai@mediatek.com>
Subject: Re: [PATCH 1/2] wifi: mac80211: add EHT MU-MIMO related flags in ieee80211_bss_conf
Date: Fri, 17 Feb 2023 09:21:17 +0000 [thread overview]
Message-ID: <791f6a25eecef8a0b30ca75acdca9bd11740acad.camel@mediatek.com> (raw)
In-Reply-To: <26c62285825010dc9947c9a8c147f60da5db004a.camel@sipsolutions.net>
On Wed, 2023-02-15 at 18:42 +0100, Johannes Berg wrote:
> On Thu, 2023-02-09 at 06:09 +0800, Ryder Lee wrote:
> > Simliar to VHT/HE. This is utilized to pass MU-MIMO configurations
>
> Typo - similar
>
> > from user space (i.e. hostap) to driver.
>
> ^^ hostapd
>
will fix.
> > + * @eht_su_beamformer: in AP-mode, does this BSS support operation
> > as an EHT SU
> > + * beamformer
> > + * @eht_su_beamformee: in AP-mode, does this BSS support operation
> > as an EHT SU
> > + * beamformee
> > + * @eht_mu_beamformer: in AP-mode, does this BSS support operation
> > as an EHT MU
> > + * beamformer
>
> Is that really about _supporting_ it rather than _using_ it? Or
> _enabling_ it?
>
Will fix. For the sake of consistency, I copy-and-pasted from VHT/HE
MU-MIMO's statement.
Ryder
prev parent reply other threads:[~2023-02-17 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 22:09 [PATCH 1/2] wifi: mac80211: add EHT MU-MIMO related flags in ieee80211_bss_conf Ryder Lee
2023-02-08 22:09 ` [PATCH 2/2] wifi: mac80211: add LDPC " Ryder Lee
2023-02-15 17:43 ` Johannes Berg
2023-02-17 9:32 ` Ryder Lee
2023-02-15 17:42 ` [PATCH 1/2] wifi: mac80211: add EHT MU-MIMO " Johannes Berg
2023-02-17 9:21 ` Ryder Lee [this message]
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=791f6a25eecef8a0b30ca75acdca9bd11740acad.camel@mediatek.com \
--to=ryder.lee@mediatek.com \
--cc=Evelyn.Tsai@mediatek.com \
--cc=Shayne.Chen@mediatek.com \
--cc=johannes@sipsolutions.net \
--cc=linux-mediatek@lists.infradead.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.