From: Maxime Bizon <mbizon@freebox.fr>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath10k@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix misreported tx bandwidth for 160Mhz
Date: Mon, 16 May 2022 18:23:25 +0200 [thread overview]
Message-ID: <c4bf5262bc250afd9c9e52248f1b576a7882c8d4.camel@freebox.fr> (raw)
In-Reply-To: <87o7zx4fue.fsf@kernel.org>
On Mon, 2022-05-16 at 19:11 +0300, Kalle Valo wrote:
Hello Kalle,
> On what ath10k hardware and afirmware version did you test this? I
> can add that to the commit log.
>
QCA9984
10.4-3.10-00047
--
Maxime
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Bizon <mbizon@freebox.fr>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath10k@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix misreported tx bandwidth for 160Mhz
Date: Mon, 16 May 2022 18:23:25 +0200 [thread overview]
Message-ID: <c4bf5262bc250afd9c9e52248f1b576a7882c8d4.camel@freebox.fr> (raw)
In-Reply-To: <87o7zx4fue.fsf@kernel.org>
On Mon, 2022-05-16 at 19:11 +0300, Kalle Valo wrote:
Hello Kalle,
> On what ath10k hardware and afirmware version did you test this? I
> can add that to the commit log.
>
QCA9984
10.4-3.10-00047
--
Maxime
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-05-16 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 15:23 [PATCH] ath10k: fix misreported tx bandwidth for 160Mhz Maxime Bizon
2022-05-16 15:23 ` Maxime Bizon
2022-05-16 16:11 ` Kalle Valo
2022-05-16 16:11 ` Kalle Valo
2022-05-16 16:23 ` Maxime Bizon [this message]
2022-05-16 16:23 ` Maxime Bizon
2022-05-16 16:35 ` Kalle Valo
2022-05-16 16:35 ` Kalle Valo
2022-05-22 12:28 ` Kalle Valo
2022-05-22 12:28 ` Kalle Valo
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=c4bf5262bc250afd9c9e52248f1b576a7882c8d4.camel@freebox.fr \
--to=mbizon@freebox.fr \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@kernel.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.