From: Kalle Valo <kvalo@codeaurora.org>
To: Maharaja Kennadyrajan <mkenna@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Fix the rate mask value for legacy and peer fixed rate
Date: Fri, 07 Jun 2019 08:05:38 +0300 [thread overview]
Message-ID: <87imtit271.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <04d8be7e61dad763b8526bf615af4730@codeaurora.org> (Maharaja Kennadyrajan's message of "Fri, 07 Jun 2019 10:31:31 +0530")
Maharaja Kennadyrajan <mkenna@codeaurora.org> writes:
> On 2019-06-06 10:24 pm, Kalle Valo wrote:
>> Maharaja Kennadyrajan <mkenna@codeaurora.org> wrote:
>>
>>> The rate mask value is changed from 0xff to oxffff (u8 to u32)
>>> in the firmware for the legacy fixed rate and peer fixed rate
>>> setting in the set bitrate command.
>>> Hence this patch is fixing the same in the driver.
>>>
>>> Signed-off-by: Maharaja Kennadyrajan <mkenna@codeaurora.org>
>>
>> Is this backwards compatible change? I'm not convinced about that.
>
> [Maha]: It won't break the backward compatibility as firmware is
> taking care of it. Firmware is using 0xffff as mask value from the
> beginning and this change is not added recently in the firmware.
Good, thanks for the clarification.
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-06-07 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:37 [PATCH] ath11k: Fix the rate mask value for legacy and peer fixed rate Maharaja Kennadyrajan
2019-06-06 16:54 ` Kalle Valo
[not found] ` <20190606165407.65AC460DAB@smtp.codeaurora.org>
2019-06-07 5:01 ` Maharaja Kennadyrajan
2019-06-07 5:05 ` Kalle Valo [this message]
2019-06-07 7:48 ` Maharaja Kennadyrajan
2019-06-12 8:13 ` 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=87imtit271.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=mkenna@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 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.