From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Tony Chuang <yhchuang@realtek.com>,
"Larry.Finger\@lwfinger.net" <Larry.Finger@lwfinger.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>, Pkshih <pkshih@realtek.com>,
Andy Huang <tehuang@realtek.com>
Subject: Re: [PATCH v2 13/13] rtw88: add support for Realtek 802.11ac wireless chips
Date: Tue, 29 Jan 2019 10:59:22 +0200 [thread overview]
Message-ID: <875zu7zvo5.fsf@codeaurora.org> (raw)
In-Reply-To: <CA+ASDXOWfFqZRyWbsb=WqORDvsVD+HjNmbGON9R1kOL88=aKew@mail.gmail.com> (Brian Norris's message of "Mon, 28 Jan 2019 13:01:29 -0800")
Brian Norris <briannorris@chromium.org> writes:
> Hi,
>
> On Sun, Jan 27, 2019 at 7:36 PM Tony Chuang <yhchuang@realtek.com> wrote:
>> > -----Original Message-----
>> > From: Brian Norris [mailto:briannorris@chromium.org]
>> >
>> > On Fri, Nov 16, 2018 at 07:31:19PM +0800, yhchuang@realtek.com wrote:
>> > > diff --git a/MAINTAINERS b/MAINTAINERS
>> > > index 9ad052a..138515b 100644
>> > > --- a/MAINTAINERS
>> > > +++ b/MAINTAINERS
>> > > @@ -12546,6 +12546,14 @@ T: git
>> > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.g
>> > > S: Maintained
>> > > F: drivers/net/wireless/realtek/rtlwifi/
>> > >
>> > > +REALTEK WIRELESS DRIVER (rtw88)
>> > > +M: Yan-Hsuan Chuang <yhchuang@realtek.com>
>> > > +L: linux-wireless@vger.kernel.org
>> > > +W: http://wireless.kernel.org/
>> > > +T: git
>> > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
>> >
>> > That tree hasn't been updated in years. I expect that's not relevant, so
>> > perhaps you should remove it? I think these days, unless you have a
>> > large amount of patches that deserves its own tree / pull-request,
>> > you're probably just going to be covered by the wireless-drivers /
>> > wireless-drivers-next trees:
>> >
>> > NETWORKING DRIVERS (WIRELESS)
>> > M: Kalle Valo <kvalo@codeaurora.org>
>> > L: linux-wireless@vger.kernel.org
>> > Q: http://patchwork.kernel.org/project/linux-wireless/list/
>> > T: git
>> > git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git
>> > T: git
>> > git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
>>
>> OK, I can change to wireless-drivers tree and send PATCHv3.
>
> I wouldn't list wireless-drivers directly -- you don't need to list
> any tree at all, and the "NETWORKING DRIVERS (WIRELESS)" entry will
> cover you anyway.
I agree, no need to duplicate the git tree entry for every driver. The
top level "NETWORKING DRIVERS (WIRELESS)" entry should be enough.
--
Kalle Valo
next prev parent reply other threads:[~2019-01-29 8:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 11:31 [PATCH v2 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips yhchuang
2018-11-16 11:31 ` [PATCH v2 01/13] rtw88: main files yhchuang
2018-12-07 8:23 ` Tony Chuang
2018-12-13 9:46 ` Kalle Valo
2018-11-16 11:31 ` [PATCH v2 02/13] rtw88: core files yhchuang
2018-11-16 11:31 ` [PATCH v2 03/13] rtw88: hci files yhchuang
2018-11-16 11:31 ` [PATCH v2 04/13] rtw88: trx files yhchuang
2018-11-16 11:31 ` [PATCH v2 05/13] rtw88: mac files yhchuang
2018-11-16 11:31 ` [PATCH v2 06/13] rtw88: fw and efuse files yhchuang
2018-11-16 11:31 ` [PATCH v2 07/13] rtw88: phy files yhchuang
2018-11-16 11:31 ` [PATCH v2 08/13] rtw88: debug files yhchuang
2018-11-16 11:31 ` [PATCH v2 09/13] rtw88: chip files yhchuang
2018-11-16 11:31 ` [PATCH v2 10/13] rtw88: 8822B init table yhchuang
2018-11-16 11:31 ` [PATCH v2 11/13] rtw88: 8822C " yhchuang
2018-11-16 11:31 ` [PATCH v2 12/13] rtw88: Kconfig & Makefile yhchuang
2018-11-16 11:31 ` [PATCH v2 13/13] rtw88: add support for Realtek 802.11ac wireless chips yhchuang
2019-01-22 21:34 ` Brian Norris
2019-01-28 3:36 ` Tony Chuang
2019-01-28 21:01 ` Brian Norris
2019-01-29 8:59 ` Kalle Valo [this message]
2018-11-30 9:37 ` [PATCH v2 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips Stanislaw Gruszka
2018-12-12 9:07 ` Stanislaw Gruszka
2018-12-13 9:48 ` Kalle Valo
2019-01-08 2:48 ` Tony Chuang
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=875zu7zvo5.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=briannorris@chromium.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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).