From: Ping-Ke Shih <pkshih@realtek.com>
To: alex bestoso <alexbestoso@bestosotech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Bug Report - Rtlwifi
Date: Thu, 27 Nov 2025 07:50:22 +0000 [thread overview]
Message-ID: <4e2592fe3ec242ba9a8d380ed4e16cc3@realtek.com> (raw)
In-Reply-To: <fcd02348-804c-459b-aa03-de61931516be@bestosotech.com>
>
> Never made a patch before; but I believe that this is correct, made with git
>
> Sent as attachment and pasted below:
>
I can send a patch based on yours.
next prev parent reply other threads:[~2025-11-27 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85517aee-6e2a-4524-a5e2-6b48d05facbe@bestosotech.com>
2025-11-27 6:37 ` Bug Report - Rtlwifi Ping-Ke Shih
2025-11-27 6:55 ` alex bestoso
2025-11-27 7:50 ` Ping-Ke Shih [this message]
2025-11-27 15:09 ` alex bestoso
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=4e2592fe3ec242ba9a8d380ed4e16cc3@realtek.com \
--to=pkshih@realtek.com \
--cc=alexbestoso@bestosotech.com \
--cc=linux-kernel@vger.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