mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>,
	Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Michael Straube" <straube.linux@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH v3 6/6] MAINTAINERS: add entry for the RTL8723B rtw88 driver
Date: Tue, 22 Sep 2026 00:28:40 +0000	[thread overview]
Message-ID: <fe3c6884a96b476799f415a06314f1ba@realtek.com> (raw)
In-Reply-To: <ffe834a8a469d5febb7e73de371d662f9a0d115f@linux.dev>

Luka Gejak <luka.gejak@linux.dev> wrote:
> September 22, 2026 at 1:35 AM, "Jeff Johnson" <jeff.johnson@oss.qualcomm.com> wrote:
> 
> 
> >
> > On 9/21/2026 11:14 AM, Johannes Berg wrote:
> >
> > >
> > > On Mon, 2026-09-21 at 16:49 +0000, Luka Gejak wrote:
> > >
> > > >
> > > > It is supposed to work in the same way it works for other driver
> > > >  maintainers. I would review patches and provide my acked by or
> > > >  reviewed by them and Ping-Ke would apply them to his rtw-next branch.
> > > >
> > >
> > >  I don't think we have a lot of folks below the driver maintainers who s
> > >  end me pull requests (except Toke maybe?) - but as long as I don't need
> > >  to deal with it I'm happy, you can figure it out between yourselves :)
> > >
> > For ath.git there are sub-maintainers for ath5k (Multiple), ath9k (Toke),
> > carl9170 (Christian), and wcn36xx (Loic).
> >
> > Toke has a linux-wireless patchwork account so the ath9k patches are initially
> > assigned to him in patchwork, and he Acks on the list and assigns the
> > patchwork records to me when he approves patches.
> >
> > For the others the maintainers just Ack on the list, and I take them from there.
> >
> > So the question is do how do you want to handle this in patchwork?
> >
> > /jeff
> >
> 
> What do you think makes more sense here: patchwork delegate
> access like Toke has for ath9k, or on list ack based? I'd lean
> towards delegate access if it's not a big ask on your end, but
> happy to go with whatever works best operationally for you.

I'm happy that people join rtw88 reviewers. 

Personally I prefer people give Reviewed-by tag to the patches, and
I can myself take the patches by patchwork state and send pull-request
to Johannes. 

With additional flows of patchwork and pull-request, it looks much
hard to maintain, since I don't think there will be a lot of patches of
drivers/net/wireless/realtek/rtw88/rtw8723b*.{c,h}

By the way, if you are interested in rtw88, maybe add a "R:"
entry to be a reviewer of rtw88?

Ping-Ke


  reply	other threads:[~2026-09-22  0:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 15:43 [PATCH v3 0/6] wifi: rtw88: add RTL8723B/RTL8723BS support Luka Gejak
2026-09-21 15:43 ` [PATCH v3 1/6] wifi: rtw88: 8723b: add the RTL8723B register definitions Luka Gejak
2026-09-23  7:44   ` Ping-Ke Shih
2026-09-21 15:43 ` [PATCH v3 2/6] wifi: rtw88: 8723b: add the RTL8723B BB, RF and AGC tables Luka Gejak
2026-09-23  7:50   ` Ping-Ke Shih
2026-09-23  8:27     ` Luka Gejak
2026-09-23  8:34       ` Ping-Ke Shih
2026-09-23  8:44         ` Luka Gejak
2026-09-23  8:59           ` Ping-Ke Shih
2026-09-23  9:09             ` Luka Gejak
2026-09-21 15:43 ` [PATCH v3 3/6] wifi: rtw88: 8723b: add the RTL8723B chip driver Luka Gejak
2026-09-23  8:30   ` Ping-Ke Shih
2026-09-23 21:50     ` Luka Gejak
2026-09-24  3:11       ` Ping-Ke Shih
2026-09-24  8:30         ` Luka Gejak
2026-09-21 15:43 ` [PATCH v3 4/6] wifi: rtw88: 8723bs: add the RTL8723BS SDIO bind Luka Gejak
2026-09-23  9:04   ` Ping-Ke Shih
2026-09-21 15:43 ` [PATCH v3 5/6] wifi: rtw88: 8723bs: enable building the RTL8723BS driver Luka Gejak
2026-09-21 15:43 ` [PATCH v3 6/6] MAINTAINERS: add entry for the RTL8723B rtw88 driver Luka Gejak
2026-09-21 16:25   ` Johannes Berg
2026-09-21 16:49     ` Luka Gejak
2026-09-21 18:14       ` Johannes Berg
2026-09-21 22:35         ` Jeff Johnson
2026-09-21 23:53           ` Luka Gejak
2026-09-22  0:28             ` Ping-Ke Shih [this message]
2026-09-22  0:43               ` Luka Gejak
2026-09-22  0:50                 ` Ping-Ke Shih
2026-09-22  1:07                   ` Luka Gejak
2026-09-24  1:42                     ` Ping-Ke Shih
2026-09-24 17:43                       ` 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=fe3c6884a96b476799f415a06314f1ba@realtek.com \
    --to=pkshih@realtek.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=pbrobinson@gmail.com \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=straube.linux@gmail.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

all inboxes | Powered by JetHome®