From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Chuang <yhchuang@realtek.com>
Cc: Bjoern Franke <bjo@schafweide.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: Realtek 8822BE: r8822be vs. rtwpci (mainline / lwfinger)
Date: Fri, 13 Dec 2019 09:25:58 +0200 [thread overview]
Message-ID: <87h824zny1.fsf@codeaurora.org> (raw)
In-Reply-To: <e28ce50db6344157832fc860a65a3ae9@realtek.com> (Tony Chuang's message of "Fri, 13 Dec 2019 06:37:17 +0000")
Tony Chuang <yhchuang@realtek.com> writes:
>> 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.
Great, thanks.
> 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.
Yeah, that's not so important but good to have anyway. I think you
should start with symbols marked with EXPORT_SYMBOL().
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-12-13 7:26 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
2019-12-13 7:25 ` Kalle Valo [this message]
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=87h824zny1.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=bjo@schafweide.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yhchuang@realtek.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.