mirror of https://lore.kernel.org/ath12k/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Wen Gong <quic_wgong@quicinc.com>, linux-wireless@vger.kernel.org
Cc: ath12k@lists.infradead.org, quic_rkaliapp@quicinc.com
Subject: Re: [PATCH 61/76] wifi: nl80211: add EML/MLD capabilities to per-iftype capabilities
Date: Fri, 11 Aug 2023 11:03:01 +0200	[thread overview]
Message-ID: <f577425e2d4fd6141c29bcbfbea919565da9326d.camel@sipsolutions.net> (raw)
In-Reply-To: <d2f17799-6d90-9d72-a389-565163d723d2@quicinc.com>

On Fri, 2023-08-11 at 11:51 +0800, Wen Gong wrote:
> Now there are many nl80211_band such as NL80211_BAND_2GHZ/
> NL80211_BAND_5GHZ/NL80211_BAND_6GHZ... In the same interface, if some bands
> support EML, and other bands not support EML, then how to handler this
> case?

But ... these are MLD capabilities, not of the (associated) STA?

So not sure how that would make sense? What would you even _do_ with
that?

johannes

-- 
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k

  reply	other threads:[~2023-08-11  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220713094502.163926-1-johannes@sipsolutions.net>
     [not found] ` <20220713114426.4dfc9ebd0461.Ice7b841051cfeb23da17bb2caa0e45191b34c4db@changeid>
2023-08-11  3:51   ` [PATCH 61/76] wifi: nl80211: add EML/MLD capabilities to per-iftype capabilities Wen Gong
2023-08-11  9:03     ` Johannes Berg [this message]
2023-08-11  9:05       ` Wen Gong
2023-08-11  9:08         ` Johannes Berg
2023-08-11  9:24           ` Wen Gong
2023-08-11  9:27             ` Johannes Berg
2023-08-11  9:54               ` Wen Gong

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=f577425e2d4fd6141c29bcbfbea919565da9326d.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_rkaliapp@quicinc.com \
    --cc=quic_wgong@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