All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karthikeyan Periyasamy <periyasa@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: fix extended stats update issue
Date: Thu, 20 Jun 2019 19:29:52 +0530	[thread overview]
Message-ID: <df48ce5832352029971c15cbc8e1dee4@codeaurora.org> (raw)
In-Reply-To: <20190620134957.7A6726137D@smtp.codeaurora.org>

On 2019-06-20 19:19, Kalle Valo wrote:
> Karthikeyan Periyasamy <periyasa@codeaurora.org> wrote:
> 
>> user not able to see the valid tx stats. htt stats update
>> process get failed due to the wrong argument pass to
>> ath11k_get_ar_by_pdev_id API. Expected argument is pdev_id not
>> the pdev index. so avoid the conversion logic of pdev id to pdev
>> index in htt stats update process.
>> 
>> Signed-off-by: Karthikeyan Periyasamy <periyasa@codeaurora.org>
> 
> This was already applied, right?

Yes, Its already applied

https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath11k-bringup&id=b24d6461d9cf254e512a91ca430be59e70da0d5d


> 
> error: patch failed: drivers/net/wireless/ath/ath11k/dp_rx.c:1294
> error: drivers/net/wireless/ath/ath11k/dp_rx.c: patch does not apply
> stg import: Diff does not apply cleanly
> 
> Patch set to Rejected.

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  parent reply	other threads:[~2019-06-20 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  4:35 [PATCH] ath11k: fix extended stats update issue Karthikeyan Periyasamy
2019-06-20 13:49 ` Kalle Valo
     [not found] ` <20190620134957.7A6726137D@smtp.codeaurora.org>
2019-06-20 13:59   ` Karthikeyan Periyasamy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-17 13:27 Karthikeyan Periyasamy
2019-06-17 14:26 ` John Crispin
2019-06-18 12:25 ` 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=df48ce5832352029971c15cbc8e1dee4@codeaurora.org \
    --to=periyasa@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@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.