From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: JunASAKA <JunASAKA@zzy040330.moe>, Jes.Sorensen@gmail.com
Cc: kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: reply to Bitterblue Smith
Date: Tue, 29 Nov 2022 17:16:47 +0200 [thread overview]
Message-ID: <8736307b-8b09-6cc2-bf89-8ee77f1af62b@gmail.com> (raw)
In-Reply-To: <20221129143225.376856-1-JunASAKA@zzy040330.moe>
On 29/11/2022 16:32, JunASAKA wrote:
> Hi Bitterblue Smith,
>
> Thanks for your reply. I've seen the discussion.
> As for the bugs of the module, my Tenda U1 wifi module which is using the rtl8192eu chip running into problems with the rtl8xxxu module, more information can be found here: https://bugzilla.kernel.org/show_bug.cgi?id=216746. I want to solve this problem but I haven't got enough experience upon it. I'll appreciate it if you could do me a favour on it. Thanks again.
>
> Jun ASAKA.
My only idea is to compare all the code with the working driver.
I'm still busy with other things, though.
next prev parent reply other threads:[~2022-11-29 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 4:34 [PATCH] drivers: rewrite and remove a superfluous parameter JunASAKA
2022-11-29 14:06 ` Bitterblue Smith
2022-12-06 17:59 ` Arend Van Spriel
2022-12-06 18:19 ` Arend Van Spriel
2022-12-06 18:40 ` Bitterblue Smith
2022-12-06 19:14 ` Arend Van Spriel
2022-11-29 14:32 ` reply to Bitterblue Smith JunASAKA
2022-11-29 15:16 ` Bitterblue Smith [this message]
2022-11-29 14:55 ` JunASAKA
2022-11-29 15:22 ` JunASAKA
2022-11-29 15:55 ` reply to Bitterblue Smith (was [PATCH] drivers: rewrite and remove a superfluous parameter.) Willy Tarreau
2022-11-29 23:11 ` [PATCH] drivers: rewrite and remove a superfluous parameter JunASAKA
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=8736307b-8b09-6cc2-bf89-8ee77f1af62b@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=Jes.Sorensen@gmail.com \
--cc=JunASAKA@zzy040330.moe \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).