From: Kalle Valo <kvalo@codeaurora.org>
To: Peter Oh <peter.oh@bowerswilkins.com>
Cc: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
"ath10k\@lists.infradead.org" <ath10k@lists.infradead.org>,
Zhi Chen <zhichen@codeaurora.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix incorrect multicast/broadcast rate setting
Date: Thu, 07 Feb 2019 16:42:57 +0200 [thread overview]
Message-ID: <87lg2r8xse.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <6a59f346-5c9b-190c-feef-39393d17933b@bowerswilkins.com> (Peter Oh's message of "Tue, 11 Dec 2018 19:22:38 +0000")
Peter Oh <peter.oh@bowerswilkins.com> writes:
> On 12/10/2018 08:56 PM, Pradeep Kumar Chitrapu wrote:
>> From: Pradeep kumar Chitrapu <pradeepc@codeaurora.org>
>>
>> Invalid rate code is sent to firmware when multicast rate value of 0 is
>> sent to driver indicating disabled case, causing broken mesh path.
>> so fix that.
>>
>> Tested on QCA9984 with firmware 10.4-3.6.1-00827
>>
> Test data is too small. You need to provide at least QCA9880 and QCA4019
> data together which share ath10k for mesh.
Pradeep, did you test those? Or someone else?
But isn't the firmware almost the same on those hardware anyway?
--
Kalle Valo
next prev parent reply other threads:[~2019-02-07 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 4:56 [PATCH] ath10k: fix incorrect multicast/broadcast rate setting Pradeep Kumar Chitrapu
2018-12-11 19:22 ` Peter Oh
2019-02-07 14:42 ` Kalle Valo [this message]
2019-02-25 20:00 ` Sven Eckelmann
2019-02-26 9:23 ` Sven Eckelmann
2019-04-03 12:28 ` Kalle Valo
2019-04-03 13:04 ` Sven Eckelmann
2019-04-29 14:43 ` 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=87lg2r8xse.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@bowerswilkins.com \
--cc=pradeepc@codeaurora.org \
--cc=zhichen@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).