linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
To: Karthikeyan periyasamy <periyasa@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Miles Hu <milehu@codeaurora.org>, John Crispin <john@phrozen.org>,
	pradeepc=codeaurora.org@codeaurora.org
Subject: Re: [PATCH v7 1/3] ath11k: switch to using ieee80211_tx_status_ext()
Date: Thu, 18 Mar 2021 13:24:44 -0700	[thread overview]
Message-ID: <dde25ece7fcbc6a0f268c98aa461d792@codeaurora.org> (raw)
In-Reply-To: <65a8f70609a1758611c97205abd205f2@codeaurora.org>

>> +	spin_lock_bh(&ab->base_lock);
>> +	peer = ath11k_peer_find_by_id(ab, ts->peer_id);
>> +	if (peer) {
>> +		arsta = (struct ath11k_sta *)peer->sta->drv_priv;
>> +		status.sta = peer->sta;
>> +		status.skb = msdu;
>> +		status.info = info;
>> +		status.rate = &arsta->last_txrate;
>> +	}
>> +	rcu_read_unlock();
>> +	if (peer)
>> +		ieee80211_tx_status_ext(ar->hw, &status);
>> +	else
>> +		dev_kfree_skb_any(msdu);
>> +	spin_unlock_bh(&ab->base_lock);
> 
> Why ieee80211_tx_status_ext() kept under spin_lock?
> 
> Thanks,
> Karthikeyan P
Thanks Karthikeyan for the review..Yes, spin lock could be avoided for
ieee80211_tx_status_ext(). I will address this in next revision.

Thanks
pradeep

  reply	other threads:[~2021-03-18 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 23:03 [PATCH v7 0/3] ath11k: add HE radiotap header support Pradeep Kumar Chitrapu
2021-03-05 23:03 ` [PATCH v7 1/3] ath11k: switch to using ieee80211_tx_status_ext() Pradeep Kumar Chitrapu
2021-03-15 16:43   ` Karthikeyan periyasamy
2021-03-18 20:24     ` Pradeep Kumar Chitrapu [this message]
2021-03-05 23:03 ` [PATCH v7 2/3] ath11k: decode HE status tlv Pradeep Kumar Chitrapu
2021-03-05 23:03 ` [PATCH v7 3/3] ath11k: translate HE status to radiotap format Pradeep Kumar Chitrapu

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=dde25ece7fcbc6a0f268c98aa461d792@codeaurora.org \
    --to=pradeepc@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=john@phrozen.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=milehu@codeaurora.org \
    --cc=periyasa@codeaurora.org \
    --cc=pradeepc=codeaurora.org@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 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).