From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <phhuang@realtek.com>, <kevin_yang@realtek.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v6 2/5] wifi: rtw89: add function to wait for completion of TX skbs
Date: Fri, 14 Apr 2023 15:05:50 +0300 [thread overview]
Message-ID: <87ildy7joh.fsf@kernel.org> (raw)
In-Reply-To: <20230411124832.14965-3-pkshih@realtek.com> (Ping-Ke Shih's message of "Tue, 11 Apr 2023 20:48:29 +0800")
Ping-Ke Shih <pkshih@realtek.com> writes:
> From: Po-Hao Huang <phhuang@realtek.com>
>
> Allocate a per-skb completion to track those skbs we are interested in
> and wait for them to complete transmission with TX status.
>
> Normally, the completion object is freed by wait side, but it could be
> timeout result that complete side should free the object instead. Add a
> owner field with a spin_lock to determine which side should free the
> object.
I'll change the last sentence to mention RCU so that it matches the code.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-04-14 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 12:48 [PATCH v6 0/5] wifi: rtw89: preparation of multiple interface concurrency support Ping-Ke Shih
2023-04-11 12:48 ` [PATCH v6 1/5] wifi: rtw89: 8852c: add beacon filter and CQM support Ping-Ke Shih
2023-04-14 12:11 ` Kalle Valo
2023-04-11 12:48 ` [PATCH v6 2/5] wifi: rtw89: add function to wait for completion of TX skbs Ping-Ke Shih
2023-04-14 12:05 ` Kalle Valo [this message]
2023-04-11 12:48 ` [PATCH v6 3/5] wifi: rtw89: add ieee80211::remain_on_channel ops Ping-Ke Shih
2023-04-11 12:48 ` [PATCH v6 4/5] wifi: rtw89: add flag check for power state Ping-Ke Shih
2023-04-11 12:48 ` [PATCH v6 5/5] wifi: rtw89: fix authentication fail during scan Ping-Ke Shih
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=87ildy7joh.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).