From: Johannes Berg <johannes@sipsolutions.net>
To: "Rameshkumar Sundaram (QUIC)" <quic_ramess@quicinc.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PATCH 1/2] mac80211: add support to configure 6GHz non-ht duplicate transmission
Date: Tue, 22 Mar 2022 16:04:21 +0100 [thread overview]
Message-ID: <babc75d310031f9f92736d5da65679ca50542849.camel@sipsolutions.net> (raw)
In-Reply-To: <DM6PR02MB493734ADBBC6C996845B9EF3E9179@DM6PR02MB4937.namprd02.prod.outlook.com>
On Tue, 2022-03-22 at 13:50 +0000, Rameshkumar Sundaram (QUIC) wrote:
> >
> So, Suggestion here is to add a new NL attribute to carry the
> information from user space for
> START_AP and SET_BEACON NL commands and use it here, is that
> understanding correct ?
>
Well, I was thinking it would reasonably come with the beacon rate, i.e.
as a new attribute like NL80211_TXRATE_DUP?
johannes
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-03-22 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:42 [PATCH 0/2] Add support to configure 6GHz non-ht duplicate transmission Rameshkumar Sundaram
2022-02-15 8:43 ` [PATCH 1/2] mac80211: add " Rameshkumar Sundaram
2022-03-11 11:03 ` Johannes Berg
2022-03-21 5:12 ` Rameshkumar Sundaram (QUIC)
2022-03-21 8:58 ` Johannes Berg
2022-03-22 13:50 ` Rameshkumar Sundaram (QUIC)
2022-03-22 15:04 ` Johannes Berg [this message]
2022-04-17 14:30 ` Rameshkumar Sundaram (QUIC)
2022-05-04 11:47 ` Johannes Berg
2022-02-15 8:43 ` [PATCH 2/2] ath11k: " Rameshkumar Sundaram
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=babc75d310031f9f92736d5da65679ca50542849.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_ramess@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox