From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"fiona.klute@gmx.de" <fiona.klute@gmx.de>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
"martin.kaistra@linutronix.de" <martin.kaistra@linutronix.de>,
"martin.blumenstingl@googlemail.com"
<martin.blumenstingl@googlemail.com>,
"brianwitte@mailfence.com" <brianwitte@mailfence.com>
Subject: Re: Git tree to manage Realtek WiFi drivers
Date: Wed, 20 Mar 2024 10:59:15 +0200 [thread overview]
Message-ID: <87edc5b7oc.fsf@kernel.org> (raw)
In-Reply-To: <503a9152324a817c251193ee486e1bbcb48d2fa8.camel@realtek.com> (Ping-Ke Shih's message of "Tue, 19 Mar 2024 01:33:27 +0000")
Ping-Ke Shih <pkshih@realtek.com> writes:
> First of all, thank all contributors (Cc'ed) to add new features and
> chips support of Realtek WiFi under drivers/net/wireless/realtek/.
>
> To balance load of maintainers, I will start being the maintainer to manage
> Realtek drivers [1] by an new git tree [2] that I fork from wireless-next,
> and the main branch is rtw-next. For submitters, all things are the same as
> usual except to codebase.
>
> Also welcome to help review patches from other contributors. That is
> really helpful to get these drivers better.
Ping-Ke, a big thank you for starting to maintain the rtw tree! Not only
that it helps me, I suspect Realtek driver development will be faster as
I'm not the bottleneck anymore.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-03-20 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 1:33 Git tree to manage Realtek WiFi drivers Ping-Ke Shih
2024-03-20 8:59 ` Kalle Valo [this message]
2024-03-20 9:34 ` Ping-Ke Shih
2024-03-20 17:17 ` Jeff Johnson
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=87edc5b7oc.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Jes.Sorensen@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=brianwitte@mailfence.com \
--cc=fiona.klute@gmx.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=martin.kaistra@linutronix.de \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=s.hauer@pengutronix.de \
/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