From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
Cc: "mohammed@codeaurora.org" <mohammed@codeaurora.org>,
"Raja, Tamizh Chelvam" <c_traja@qti.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [v5] ath10k: Fix broken NULL func data frame status for 10.4
Date: Thu, 8 Sep 2016 05:09:03 +0000 [thread overview]
Message-ID: <87bmzzugep.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1473151041373.34060@qti.qualcomm.com> (Mohammed Shafi Shajakhan's message of "Tue, 6 Sep 2016 08:37:22 +0000")
"Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
writes:
> please revert this patch, Raj suggested this patch introduced a
> regression in sending NULL func frames :(
>
> We will fix the wrong tx status report for NULL func frames
> appropriately (if needed in ath10k firmware) Sorry for the regression,
> kindly revert it until a proper fix is figured out.
Like we discussed privately, it is better that you send the revert (or a
fix if you find one) yourself. Then we have a proper commit log etc.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-09-08 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 8:12 [PATCH v5] ath10k: Fix broken NULL func data frame status for 10.4 Mohammed Shafi Shajakhan
2016-09-02 16:00 ` [v5] " Kalle Valo
2016-09-06 8:37 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-09-08 5:09 ` Valo, Kalle [this message]
2016-09-08 6:30 ` Mohammed Shafi Shajakhan
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=87bmzzugep.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.com \
--cc=mohammed@codeaurora.org \
--cc=mohammed@qti.qualcomm.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