From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
linux-pwm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-i2c@vger.kernel.org, groeck@chromium.org,
kernel@collabora.com, linux-rtc@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
Benson Leung <bleung@chromium.org>,
Sebastian Reichel <sre@kernel.org>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
devicetree@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-pm@vger.kernel.org, MyungJoo Ham <myungjoo.ham@samsung.com>,
Lee Jones <lee.jones@linaro.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Rob Herring <robh+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] MAINTAINERS: add maintainers for ChromeOS EC sub-drivers
Date: Thu, 13 Dec 2018 10:50:50 +0100 [thread overview]
Message-ID: <20181213095050.GM19816@piout.net> (raw)
In-Reply-To: <6f688bfe-2ebe-1934-0375-016ae859dcfb@collabora.com>
On 13/12/2018 10:30:16+0100, Enric Balletbo i Serra wrote:
> > However, you should probably indicate which tree do you expect that to
> > go through ;)
> >
>
> Well, these are sub-drivers for different subsystems but are related to the main
> ChromeOS EC. I expect all go through their specific subsystem and their
> maintainer. I.e the rtc driver go through your tree, the mfd go through Lee's
> tree, iio drivers through Jonathan's tree, etc. This is the reason I did not add
> the tree. Main purpose here as that Benson and I are aware when someone sends a
> change on one of the sub-drivers and we can review these patches.
>
Sure, sorry I was not clear but I was asking about this particular
patch because as it is, you will get acks from all the maintainers but I
think they all think someone else will apply it ;)
> Thanks,
> Enric
>
> >> ---
> >>
> >> Changes in v2:
> >> - Fix typo in Benson email address.
> >>
> >> MAINTAINERS | 24 ++++++++++++++++++++++++
> >> 1 file changed, 24 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index a24129b0b043..bbe7180e2851 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -3625,6 +3625,30 @@ S: Maintained
> >> T: git git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git
> >> F: drivers/platform/chrome/
> >>
> >> +CHROMEOS EC SUBDRIVERS
> >> +M: Benson Leung <bleung@chromium.org>
> >> +M: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> >> +S: Maintained
> >> +F: Documentation/devicetree/bindings/extcon/extcon-usbc-cros-ec.txt
> >> +F: Documentation/devicetree/bindings/input/cros-ec-keyb.txt
> >> +F: Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.txt
> >> +F: Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt
> >> +F: Documentation/devicetree/bindings/mfd/cros-ec.txt
> >> +F: Documentation/ABI/testing/sysfs-bus-iio-cros-ec
> >> +F: drivers/extcon/extcon-usbc-cros-ec.c
> >> +F: drivers/i2c/busses/i2c-cros-ec-tunnel.c
> >> +F: drivers/iio/accel/cros_ec*
> >> +F: drivers/iio/common/cros_ec_sensors/
> >> +F: drivers/iio/light/cros_ec*
> >> +F: drivers/iio/pressure/cros_ec*
> >> +F: drivers/input/keyboard/cros_ec*
> >> +F: drivers/mfd/cros_ec*
> >> +F: drivers/power/supply/cros_usbpd-charger.c
> >> +F: drivers/pwm/pwm-cros-ec.c
> >> +F: drivers/rtc/rtc-cros-ec.c
> >> +F: include/linux/iio/common/cros_ec_sensors_core.h
> >> +F: include/linux/mfd/cros_ec*
> >> +
> >> CIRRUS LOGIC AUDIO CODEC DRIVERS
> >> M: Brian Austin <brian.austin@cirrus.com>
> >> M: Paul Handrigan <Paul.Handrigan@cirrus.com>
> >> --
> >> 2.19.2
> >>
> >
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-13 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181211191040epcas2p2a15c57e7488f216d012efe553a007d43@epcas2p2.samsung.com>
2018-12-11 19:09 ` [PATCH v2] MAINTAINERS: add maintainers for ChromeOS EC sub-drivers Enric Balletbo i Serra
2018-12-11 19:13 ` Wolfram Sang
2018-12-11 23:09 ` Sebastian Reichel
2018-12-12 0:55 ` Chanwoo Choi
2018-12-12 17:06 ` Jonathan Cameron
2018-12-12 18:21 ` Benson Leung
2018-12-12 22:29 ` Alexandre Belloni
2018-12-13 9:30 ` Enric Balletbo i Serra
2018-12-13 9:50 ` Alexandre Belloni [this message]
2018-12-13 9:55 ` Enric Balletbo i Serra
2018-12-13 10:59 ` Alexandre Belloni
2018-12-13 9:22 ` Lee Jones
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=20181213095050.GM19816@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bleung@chromium.org \
--cc=cw00.choi@samsung.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nicolas.ferre@microchip.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).