From: Johannes Berg <johannes@sipsolutions.net>
To: Kang Yang <quic_kangyang@quicinc.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wifi: mac80211: supplement parsing of puncturing bitmap
Date: Thu, 14 Mar 2024 09:03:44 +0100 [thread overview]
Message-ID: <24017bc8d01a92df6a21acb244644c5d975407d5.camel@sipsolutions.net> (raw)
In-Reply-To: <4f79391f-cd81-4a3d-a236-447cb4c1f4d2@quicinc.com>
On Thu, 2024-03-14 at 11:21 +0800, Kang Yang wrote:
>
> On 3/12/2024 4:16 PM, Johannes Berg wrote:
> > On Tue, 2024-03-12 at 12:59 +0800, Kang Yang wrote:
> > > Current mac80211 won't parsing puncturing bitmap when process EHT
> > > Operation element in 6 GHz band or Bandwidth Indication element. This
> > > leads to puncturing bitmap cannot be updated in related situations, such
> > > as connecting to an EHT AP in 6 GHz band.
> > >
> > > So supplement parsing of puncturing bitmap for these elements.
> >
> > Hah, yes, I just noticed that too and fixed the second part yesterday,
> > and was still thinking about how I could test the first part :-)
> >
>
>
> So what are you planning to do with this patch?
>
> Any suggestions or you want to add puncutring bitmap parsing by your patch?
>
No no, all good. I was just commenting :)
Once the trees settle and all (we're in the middle of the merge window)
I'll apply this.
johannes
next prev parent reply other threads:[~2024-03-14 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 4:59 [PATCH 0/2] wifi: ath12k: dynamically update puncturing bitmap Kang Yang
2024-03-12 4:59 ` [PATCH 1/2] wifi: mac80211: supplement parsing of " Kang Yang
2024-03-12 8:16 ` Johannes Berg
2024-03-12 8:45 ` Kang Yang
2024-03-12 9:22 ` Kang Yang
2024-03-12 10:17 ` Johannes Berg
2024-03-14 3:21 ` Kang Yang
2024-03-14 8:03 ` Johannes Berg [this message]
2024-03-12 4:59 ` [PATCH 2/2] wifi: ath12k: dynamically update " Kang Yang
2024-03-18 8:56 ` Kang Yang
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=24017bc8d01a92df6a21acb244644c5d975407d5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_kangyang@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