From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: add Freescale pin controllers
Date: Mon, 12 Feb 2018 11:48:22 +0100 [thread overview]
Message-ID: <1518432502.2744.5.camel@pengutronix.de> (raw)
In-Reply-To: <20180210153204.12728-1-stefan@agner.ch>
Am Samstag, den 10.02.2018, 16:32 +0100 schrieb Stefan Agner:
> Add Dong Aisheng, Fabio Estevam, Shawn Guo and myself as maintainer
> and Sascha as reviewer.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> ?MAINTAINERS | 11 +++++++++++
> ?1 file changed, 11 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 82ad0eabce4f..fb672dfc519d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10768,6 +10768,17 @@ L: linux-gpio at vger.kernel.org
> ?S: Supported
> ?F: drivers/pinctrl/pinctrl-at91-pio4.*
> ?
> +PIN CONTROLLER - FREESCALE
> +M: Dong Aisheng <aisheng.dong@nxp.com>
> +M: Fabio Estevam <festevam@gmail.com>
> +M: Shawn Guo <shawnguo@kernel.org>
> +M: Stefan Agner <stefan@agner.ch>
> +R: Sascha Hauer <kernel@pengutronix.de>
I'm fine with the patch, but it might make sense to clarify this a bit:
the kernel@ address is really the whole Pengutronix kernel team, not
just Sascha. Using this address is totally fine if you expect comments
on patches, as it gives them a quite wide exposure inside of PTX.
Regards,
Lucas
> +L: linux-gpio at vger.kernel.org
> +S: Maintained
> +F: drivers/pinctrl/freescale/*
> +F: Documentation/devicetree/bindings/pinctrl/fsl,*
> +
> ?PIN CONTROLLER - INTEL
> ?M: Mika Westerberg <mika.westerberg@linux.intel.com>
> ?M: Heikki Krogerus <heikki.krogerus@linux.intel.com>
next prev parent reply other threads:[~2018-02-12 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 15:32 [PATCH] MAINTAINERS: add Freescale pin controllers Stefan Agner
2018-02-10 16:28 ` Fabio Estevam
2018-02-12 10:48 ` Lucas Stach [this message]
2018-02-12 11:22 ` Baruch Siach
2018-02-12 11:34 ` Lucas Stach
2018-02-12 11:53 ` Stefan Agner
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=1518432502.2744.5.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).