public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"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: Git tree to manage Realtek WiFi drivers
Date: Tue, 19 Mar 2024 01:33:27 +0000	[thread overview]
Message-ID: <503a9152324a817c251193ee486e1bbcb48d2fa8.camel@realtek.com> (raw)

Hi,

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

---
[1] https://lore.kernel.org/linux-wireless/20240319011925.6855-1-pkshih@realtek.com/T/#u
[2] https://github.com/pkshih/rtw.git


             reply	other threads:[~2024-03-19  1:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  1:33 Ping-Ke Shih [this message]
2024-03-20  8:59 ` Git tree to manage Realtek WiFi drivers Kalle Valo
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=503a9152324a817c251193ee486e1bbcb48d2fa8.camel@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=brianwitte@mailfence.com \
    --cc=fiona.klute@gmx.de \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=martin.kaistra@linutronix.de \
    --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