From: Kalle Valo <kvalo@codeaurora.org>
To: <yhchuang@realtek.com>
Cc: <johannes@sipsolutions.net>, <gregkh@linuxfoundation.org>,
<linux-wireless@vger.kernel.org>, <Larry.Finger@lwfinger.net>,
<sgruszka@redhat.com>, <pkshih@realtek.com>,
<tehuang@realtek.com>, <briannorris@chromium.org>
Subject: Re: [PATCH v7 00/14] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips
Date: Mon, 11 Mar 2019 15:48:15 +0200 [thread overview]
Message-ID: <87lg1l8qu8.fsf@codeaurora.org> (raw)
In-Reply-To: <1552139302-20476-1-git-send-email-yhchuang@realtek.com> (yhchuang@realtek.com's message of "Sat, 9 Mar 2019 21:48:08 +0800")
<yhchuang@realtek.com> writes:
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>
> This is a new mac80211 driver for Realtek 802.11ac wireless network chips.
> rtw88 now supports RTL8822BE/RTL8822CE now, with basic station mode
> functionalities. The firmware for both can be found at linux-firmware.
>
[...]
> Yan-Hsuan Chuang (14):
> rtw88: main files
> rtw88: core files
> rtw88: hci files
> rtw88: trx files
> rtw88: mac files
> rtw88: fw and efuse files
> rtw88: phy files
> rtw88: debug files
> rtw88: chip files
> rtw88: 8822B init table
> rtw88: 8822C init table
> rtw88: Kconfig & Makefile
> rtw88: add MAINTAINERS entry
> staging: rtlwifi: remove staging rtlwifi driver
Do note that the staging driver was too big and didn't make it to the
list (and patchwork). But no need to resend or modify that patch, just
an observation.
Or would --find-renames help to make the patch smaller?
--
Kalle Valo
next prev parent reply other threads:[~2019-03-11 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 13:48 [PATCH v7 00/14] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips yhchuang
2019-03-09 13:48 ` [PATCH v7 01/14] rtw88: main files yhchuang
2019-03-11 13:11 ` Stanislaw Gruszka
2019-03-11 13:14 ` Kalle Valo
2019-03-11 13:19 ` Stanislaw Gruszka
2019-03-11 13:32 ` Kalle Valo
2019-03-09 13:48 ` [PATCH v7 02/14] rtw88: core files yhchuang
2019-03-09 13:48 ` [PATCH v7 03/14] rtw88: hci files yhchuang
2019-03-11 12:50 ` Stanislaw Gruszka
2019-03-11 12:52 ` Johannes Berg
2019-03-09 13:48 ` [PATCH v7 04/14] rtw88: trx files yhchuang
2019-03-09 13:48 ` [PATCH v7 05/14] rtw88: mac files yhchuang
2019-03-09 13:48 ` [PATCH v7 06/14] rtw88: fw and efuse files yhchuang
2019-03-09 13:48 ` [PATCH v7 07/14] rtw88: phy files yhchuang
2019-03-09 13:48 ` [PATCH v7 08/14] rtw88: debug files yhchuang
2019-03-09 13:48 ` [PATCH v7 09/14] rtw88: chip files yhchuang
2019-03-11 13:17 ` Stanislaw Gruszka
2019-03-09 13:48 ` [PATCH v7 10/14] rtw88: 8822B init table yhchuang
2019-03-09 13:48 ` [PATCH v7 11/14] rtw88: 8822C " yhchuang
2019-03-09 13:48 ` [PATCH v7 12/14] rtw88: Kconfig & Makefile yhchuang
2019-03-09 13:48 ` [PATCH v7 13/14] rtw88: add MAINTAINERS entry yhchuang
2019-03-11 13:48 ` Kalle Valo [this message]
2019-03-11 13:58 ` [PATCH v7 00/14] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips Stanislaw Gruszka
2019-03-12 5:14 ` 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=87lg1l8qu8.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=briannorris@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=sgruszka@redhat.com \
--cc=tehuang@realtek.com \
--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 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).