From: jacopo mondi <jacopo@jmondi.org>
To: Simon Horman <horms@verge.net.au>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
geert+renesas@glider.be, laurent.pinchart@ideasonboard.com,
linus.walleij@linaro.org, linux-renesas-soc@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v4 2/4] pinctrl: sh-pfc: Fix VIN versioned groups name
Date: Wed, 7 Nov 2018 11:59:49 +0100 [thread overview]
Message-ID: <20181107105949.GC24024@w540> (raw)
In-Reply-To: <20181107104134.j2agucwh6kxhrknl@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Hi Simon,
On Wed, Nov 07, 2018 at 11:41:34AM +0100, Simon Horman wrote:
> On Tue, Nov 06, 2018 at 11:35:31AM +0100, Jacopo Mondi wrote:
> > Versioned VIN groups can appear on different sets of pins. Using the
> > VIN_DATA_PIN_GROUP macro now supports proper naming of said groups through
> > an optional 'version' argument.
> >
> > Use the 'version' argument for said macro to fix naming of versioned
> > groups for R-Car SoCs that defines them.
> >
> > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
>
> Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
>
I'm going to split this patch for each SoC to ease backporting, as
Geert suggested. Provided the single patches content is the same as
here, can I retain your R-b tag?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-11-07 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 10:35 [PATCH v4 0/4] sh-pfc: Variadic VIN_DATA_PIN_GROUP macro + updates Jacopo Mondi
2018-11-06 10:35 ` [PATCH v4 1/4] pinctrl: sh-pfc: Add optional arg to VIN_DATA_PIN_GROUP Jacopo Mondi
2018-11-07 10:40 ` Simon Horman
2018-11-08 10:58 ` Geert Uytterhoeven
2018-11-08 11:38 ` Geert Uytterhoeven
2018-11-06 10:35 ` [PATCH v4 2/4] pinctrl: sh-pfc: Fix VIN versioned groups name Jacopo Mondi
2018-11-07 10:41 ` Simon Horman
2018-11-07 10:59 ` jacopo mondi [this message]
2018-11-07 11:27 ` Simon Horman
2018-11-08 10:59 ` Geert Uytterhoeven
2018-11-08 11:06 ` jacopo mondi
2018-11-06 10:35 ` [PATCH v4 3/4] pinctrl: sh-pfc: r8a77965: Add VIN[4|5] groups/functions Jacopo Mondi
2018-11-07 10:56 ` Simon Horman
2018-11-08 12:22 ` Geert Uytterhoeven
2018-11-08 12:31 ` Geert Uytterhoeven
2018-11-06 10:35 ` [PATCH v4 4/4] pinctrl: sh-pfc: r8a77990: " Jacopo Mondi
2018-11-07 10:34 ` Simon Horman
2018-11-07 10:56 ` jacopo mondi
2018-11-08 12:37 ` Geert Uytterhoeven
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=20181107105949.GC24024@w540 \
--to=jacopo@jmondi.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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 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.