linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V2 0/2] wifi: ath11k: bug fixes in tx encap offload and ppdu stats
Date: Mon, 3 Apr 2023 09:06:01 -0700	[thread overview]
Message-ID: <667a38b0-b058-6083-6fa9-9b6d13c0c09e@quicinc.com> (raw)
In-Reply-To: <87edp1ba3j.fsf@kernel.org>


On 4/3/2023 2:15 AM, Kalle Valo wrote:
> Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com> writes:
>
>> Fixes bugs in radiotap fields and tx status reporting in TX
>> encapsulation offload cases.
>>
>> Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
>>
>> Pradeep Kumar Chitrapu (2):
>>    wifi: ath11k: fix tx status reporting in encap offload mode
>>    wifi: ath11k: Fix incorrect update of radiotap fields
> No changelog. What has changed since v1?

Thanks Kalle. Sorry about missing changelog. let me send V3 with updated 
change log..

changes are : avoid using ieee80211_tx_status_8023 and use 
ieee80211_tx_status_ext instead,
and fix commit description inorder to address previous review comments.


      reply	other threads:[~2023-04-03 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01  2:49 [PATCH V2 0/2] wifi: ath11k: bug fixes in tx encap offload and ppdu stats Pradeep Kumar Chitrapu
2023-04-01  2:49 ` [PATCH V2 1/2] wifi: ath11k: fix tx status reporting in encap offload mode Pradeep Kumar Chitrapu
2023-04-01  2:49 ` [PATCH V2 2/2] wifi: ath11k: Fix incorrect update of radiotap fields Pradeep Kumar Chitrapu
2023-04-03  9:15 ` [PATCH V2 0/2] wifi: ath11k: bug fixes in tx encap offload and ppdu stats Kalle Valo
2023-04-03 16:06   ` Pradeep Kumar Chitrapu [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=667a38b0-b058-6083-6fa9-9b6d13c0c09e@quicinc.com \
    --to=quic_pradeepc@quicinc.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.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).