From: Kevin Lo <kevlo@kevlo.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Jes Sorensen <Jes.Sorensen@gmail.com>,
Ping-Ke Shih <pkshih@realtek.com>
Subject: Re: [PATCH v2] wifi: rtl8xxxu: 8188f: no need to initialize interrupts
Date: Fri, 28 Apr 2023 14:34:54 +0800 [thread overview]
Message-ID: <ZEtpDi8oCr0E9scd@ns.kevlo.org> (raw)
In-Reply-To: <87ildgpnsd.fsf@kernel.org>
On Fri, Apr 28, 2023 at 08:40:34AM +0300, Kalle Valo wrote:
>
> Kevin Lo <kevlo@kevlo.org> writes:
>
> > There's no need to initialize interrupts for RTL8188FTV like the vendor driver.
> >
> > Signed-off-by: Kevin Lo <kevlo@kevlo.org>
>
> Why do this, what's the benefit? Or is this just a theoretical fix. The
> commit log should explain this.
If I understand correctly, just like rtw88 usb devices, rtl8xxxu has no
hardware interrupt.
next prev parent reply other threads:[~2023-04-28 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 2:34 [PATCH v2] wifi: rtl8xxxu: 8188f: no need to initialize interrupts Kevin Lo
2023-04-28 5:40 ` Kalle Valo
2023-04-28 6:34 ` Kevin Lo [this message]
2023-05-02 9:10 ` Ping-Ke Shih
2023-05-05 5:27 ` Kevin Lo
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=ZEtpDi8oCr0E9scd@ns.kevlo.org \
--to=kevlo@kevlo.org \
--cc=Jes.Sorensen@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.