linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Chuang <yhchuang@realtek.com>
To: Kalle Valo <kvalo@codeaurora.org>, Bjoern Franke <bjo@schafweide.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Realtek 8822BE: r8822be vs. rtwpci (mainline / lwfinger)
Date: Fri, 13 Dec 2019 06:37:17 +0000	[thread overview]
Message-ID: <e28ce50db6344157832fc860a65a3ae9@realtek.com> (raw)
In-Reply-To: <0101016eea4be8c6-86cd4509-2811-4de8-92be-bd5cfa50d49c-000000@us-west-2.amazonses.com>

> Subject: Re: Realtek 8822BE: r8822be vs. rtwpci (mainline / lwfinger)
> 
> Bjoern Franke <bjo@schafweide.org> writes:
> 
> > I'm a little confused about the status of the modules for the Realtek
> > 8822BE.
> >
> > Once, there was r8822be which had some issues, but worked more or less
> > reliable. Then came rtw88/rtwpci and in my Thinkpad A275 it is hardly
> 
> Tony, that rtwpci sounds like very confusing name for a rtw88 module,
> even I was first confused what driver is that. I think it should be
> rtw88_pci or something like that.
> 

True, I can rename it to rtw88_pci. I am also thinking if I should rename
all of the prefixes from "rtw_" to "rtw88_", but that seems to be a huge
patch. I will try to see if this is necessary to do it.

Yan-Hsuan

  reply	other threads:[~2019-12-13  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 16:48 Realtek 8822BE: r8822be vs. rtwpci (mainline / lwfinger) Bjoern Franke
2019-12-09 10:54 ` Kalle Valo
2019-12-13  6:37   ` Tony Chuang [this message]
2019-12-13  7:25     ` Kalle Valo

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=e28ce50db6344157832fc860a65a3ae9@realtek.com \
    --to=yhchuang@realtek.com \
    --cc=bjo@schafweide.org \
    --cc=kvalo@codeaurora.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;
as well as URLs for NNTP newsgroup(s).