From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Kever Yang <kever.yang@rock-chips.com>,
linux-rockchip@lists.infradead.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH] MAINTAINERS: rockchip: Track more files
Date: Fri, 13 Dec 2019 11:35:28 +0100 [thread overview]
Message-ID: <20191213113528.2e06e1f4@xps13> (raw)
In-Reply-To: <3160577.NKkQCOVCmZ@phil>
Hi Heiko,
Heiko Stuebner <heiko@sntech.de> wrote on Fri, 13 Dec 2019 11:27:29
+0100:
> Am Montag, 9. Dezember 2019, 09:18:00 CET schrieb Kever Yang:
> > Hi Miquel,
> >
> > On 2019/12/4 下午5:07, Miquel Raynal wrote:
> > > The current list misses a lot of drivers not prefixed or suffixed by
> > > "rockchip". For instance, there are plenty drivers called rk808 and
> > > rk805 which are currently not tracked (clk, regulator, pinctrl, RTC,
> > > MFD, includes, bindings). Add them to the list under the Rockchip
> > > entry.
> > >
> > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > > ---
> > >
> > > Hi Heiko,
> > >
> > > You are right we should try to check more often your tree. Also, here
> > > is a patch so that you are Cc'ed for all Rockchip related patches
> > > because the current list is not exhaustive at all (not sure it is
> > > voluntary or not though).
> > >
> > > Cheers,
> > > Miquèl
> > >
> > > MAINTAINERS | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index cba1095547fd..a9564e6cb872 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -2198,12 +2198,16 @@ L: linux-rockchip@lists.infradead.org
> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
> > > S: Maintained
> > > F: Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
> > > +F: Documentation/devicetree/bindings/*/*rk80*
> > > F: arch/arm/boot/dts/rk3*
> > > F: arch/arm/boot/dts/rv1108*
> > > F: arch/arm/mach-rockchip/
> > > +F: include/*/*/rk808.h
> > > +F: include/*/*/*/rk808.h
> > > F: drivers/clk/rockchip/
> > > F: drivers/i2c/busses/i2c-rk3x.c
> > > F: drivers/*/*rockchip*
> > > +F: drivers/*/*rk80*
> > > F: drivers/*/*/*rockchip*
> > > F: sound/soc/rockchip/
> > > N: rockchip
> > For the Rockchip PMIC, is it better to have a NEW MAINTAINER entry like
> > "ROCKCHIP PMIC DRIVER"
> > which share the same mailing list linux-rockchip@, because there is not
> > only rk808,
> > but also rk805, rk809, rk817, rk818, and may be more to come.
> >
> > BTW, we should use 'rk8' instead of 'rk80' to match all the Rockchip PMICs.
>
> yep, I agree with Kever on this ... also that new pmic-related entry should
> not really link to a git tree as patches for it will get distributed through
> multiple trees (mfd, regulator, rtc) most of the time.
I think it is important that the maintainer receive all Rockchip
related patches, as he has the bigger picture in mind. Of course it is
possible to add an additional MAINTAINER entry for Rockchip PMIC
drivers specifically.
So in the end, I will s/rk80/rk8/, shall I remove a specific entry from
the 4 added?
>
> Miquel can you do a v2 please?
Of course, this is planned, I'm just a bit late in my e-mail backlog!
Cheers,
Miquèl
prev parent reply other threads:[~2019-12-13 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 9:07 [PATCH] MAINTAINERS: rockchip: Track more files Miquel Raynal
2019-12-04 9:07 ` Miquel Raynal
2019-12-09 8:18 ` Kever Yang
[not found] ` <e4dc0f27-6a26-3b29-11fd-231f686fce91-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2019-12-13 10:27 ` Heiko Stuebner
2019-12-13 10:27 ` Heiko Stuebner
2019-12-13 10:35 ` Miquel Raynal [this message]
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=20191213113528.2e06e1f4@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maxime.chevallier@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.