From: jacopo mondi <jacopo@jmondi.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Chris Brandt <chris.brandt@renesas.com>,
Phil Edworthy <phil.edworthy@renesas.com>,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add Renesas RZ/A and RZ/N files to Renesas pinctrl section
Date: Tue, 16 Oct 2018 18:55:46 +0200 [thread overview]
Message-ID: <20181016165546.GC11703@w540> (raw)
In-Reply-To: <20181016115653.12810-1-geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hi Geert,
On Tue, Oct 16, 2018 at 01:56:53PM +0200, Geert Uytterhoeven wrote:
> Add paths for the Renesas RZ/A and RZ/N series pin controller drivers,
> as they are not under sh-pfc/, but still maintained with the other
> Renesas pin controller drivers.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
Thank you
j
> ---
> To be queued in sh-pfc-for-v4.21.
>
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 809600de0b7293c8..77ff83bc09464c1f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11672,6 +11672,7 @@ M: Geert Uytterhoeven <geert+renesas@glider.be>
> L: linux-renesas-soc@vger.kernel.org
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git sh-pfc
> S: Maintained
> +F: drivers/pinctrl/pinctrl-rz*
> F: drivers/pinctrl/sh-pfc/
>
> PIN CONTROLLER - SAMSUNG
> --
> 2.17.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-10-17 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 11:56 [PATCH] MAINTAINERS: Add Renesas RZ/A and RZ/N files to Renesas pinctrl section Geert Uytterhoeven
2018-10-16 16:48 ` Simon Horman
2018-10-16 16:55 ` jacopo mondi [this message]
2018-10-30 11:56 ` Linus Walleij
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=20181016165546.GC11703@w540 \
--to=jacopo@jmondi.org \
--cc=chris.brandt@renesas.com \
--cc=geert+renesas@glider.be \
--cc=jacopo+renesas@jmondi.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=phil.edworthy@renesas.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.