From: Ping-Ke Shih <pkshih@realtek.com>
To: "d.morgun@ispras.ru" <d.morgun@ispras.ru>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: RE: [PATCH rtw-next v3] wifi: rtw89: check return values in rtw89_ops_start_ap()
Date: Mon, 6 Jul 2026 01:28:14 +0000 [thread overview]
Message-ID: <a2bab03c876345bbaebf5f05f99040f2@realtek.com> (raw)
In-Reply-To: <6754361d578f7418fe85e1aec8a6b618@ispras.ru>
d.morgun@ispras.ru <d.morgun@ispras.ru> wrote:
> Hi Ping-Ke,
>
> Sorry for the confusion. The v3 suffix was added by mistake during local
> iterations of the patch.
>
> There is no public v1/v2 in the mailing list history. This is the first
> version submitted upstream.
>
> I will resend as v1 if needed.
No need to resend. I have merged this patch.
Thanks
Ping-Ke
next prev parent reply other threads:[~2026-07-06 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 9:44 [PATCH rtw-next v3] wifi: rtw89: check return values in rtw89_ops_start_ap() Dmitry Morgun
2026-06-30 0:27 ` Ping-Ke Shih
2026-07-03 15:53 ` d.morgun
2026-07-06 1:28 ` Ping-Ke Shih [this message]
2026-07-03 3:51 ` 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=a2bab03c876345bbaebf5f05f99040f2@realtek.com \
--to=pkshih@realtek.com \
--cc=d.morgun@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.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