From: Kalle Valo <kvalo@codeaurora.org>
To: Sathishkumar Muruganandam <murugana@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: remove deprecated WMI PEER stats
Date: Wed, 17 Jul 2019 17:09:18 +0300 [thread overview]
Message-ID: <87ftn43g8h.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <4b49f72c171a37529d6edc8dd382e225@codeaurora.org> (Sathishkumar Muruganandam's message of "Wed, 17 Jul 2019 18:59:16 +0530")
Sathishkumar Muruganandam <murugana@codeaurora.org> writes:
> On 2019-07-17 18:21, Kalle Valo wrote:
>> Sathishkumar Muruganandam <murugana@codeaurora.org> writes:
>>
>>> Removing WMI PEER stats which has been deprecated in FW and
>>> rx_duration of
>>> a peer is now fetched from HTT PPDU_END stats.
>>>
>>> Signed-off-by: Sathishkumar Muruganandam <murugana@codeaurora.org>
>>
>> This does not apply and sha1 id is invalid. Please use ath11k-bringup
>> branch as the baseline, do NOT have any other patches applied.
>>
>> Applying: ath11k: remove deprecated WMI PEER stats
>> fatal: sha1 information is lacking or useless
>> (drivers/net/wireless/ath/ath11k/wmi.c).
>> error: could not build fake ancestor
>> Patch failed at 0001 ath11k: remove deprecated WMI PEER stats
>
> Sorry, my bad. There was an older patch applied before this.
>
> Corrected and sent v2 patch, please check.
I was able to apply v2 to pending-ath11k branch, thanks.
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-07-17 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 5:51 [PATCH] ath11k: remove deprecated WMI PEER stats Sathishkumar Muruganandam
2019-07-17 12:51 ` Kalle Valo
2019-07-17 13:29 ` Sathishkumar Muruganandam
2019-07-17 14:09 ` Kalle Valo [this message]
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=87ftn43g8h.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=murugana@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.