From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-pfc: r8a7778: Remove outdated comments
Date: Tue, 23 Apr 2013 11:07:52 +0000 [thread overview]
Message-ID: <2250366.VB8doyBIfi@avalon> (raw)
In-Reply-To: <1366194463-27045-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Morimoto-san,
On Wednesday 17 April 2013 17:24:49 Kuninori Morimoto wrote:
> Hi Laurent
>
> Thank you for your patch
> At first, I'm sorry, these comments created confusion.
> But, these are indicating caution of strange VI pin settings.
> You can find same meaning comments on /* IPSR9 */ category, as /* see
> sel_vi0 */ So, How about this ?
>
> /* see VI0_Rx_A_MARK */
>
> or
>
> /* see sel_vi0 */
That sounds good to me. I'll resubmit the patch.
> > Function GPIOs have been removed, remove comments that refer to them.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >
> > drivers/pinctrl/sh-pfc/pfc-r8a7778.c | 26 +++++++++++++-------------
> > 1 file changed, 13 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> > b/drivers/pinctrl/sh-pfc/pfc-r8a7778.c index ddbd27b..e9cc040 100644
> > --- a/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> > +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7778.c
> > @@ -376,19 +376,19 @@ enum {
> >
> > AVS1_MARK,
> > AVS2_MARK,
> >
> > - VI0_R0_C_MARK, /* see GPIO_FN_VI0_R0_A */
> > - VI0_R1_C_MARK, /* see GPIO_FN_VI0_R1_A */
> > - VI0_R2_C_MARK, /* see GPIO_FN_VI0_R2_A */
> > - /* VI0_R3_C_MARK, see GPIO_FN_VI0_R3_A */
> > - VI0_R4_C_MARK, /* see GPIO_FN_VI0_R4_A */
> > - VI0_R5_C_MARK, /* see GPIO_FN_VI0_R5_A */
> > -
> > - VI0_R0_D_MARK, /* see GPIO_FN_VI0_R0_B */
> > - VI0_R1_D_MARK, /* see GPIO_FN_VI0_R1_B */
> > - VI0_R2_D_MARK, /* see GPIO_FN_VI0_R2_B */
> > - VI0_R3_D_MARK, /* see GPIO_FN_VI0_R3_B */
> > - VI0_R4_D_MARK, /* see GPIO_FN_VI0_R4_B */
> > - VI0_R5_D_MARK, /* see GPIO_FN_VI0_R5_B */
> > + VI0_R0_C_MARK,
> > + VI0_R1_C_MARK,
> > + VI0_R2_C_MARK,
> > + /* VI0_R3_C_MARK, */
> > + VI0_R4_C_MARK,
> > + VI0_R5_C_MARK,
> > +
> > + VI0_R0_D_MARK,
> > + VI0_R1_D_MARK,
> > + VI0_R2_D_MARK,
> > + VI0_R3_D_MARK,
> > + VI0_R4_D_MARK,
> > + VI0_R5_D_MARK,
> >
> > /* IPSR0 */
> > PRESETOUT_MARK, PWM1_MARK, AUDATA0_MARK,
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-04-23 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 10:27 [PATCH] sh-pfc: r8a7778: Remove outdated comments Laurent Pinchart
2013-04-18 0:24 ` Kuninori Morimoto
2013-04-23 11:07 ` Laurent Pinchart [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=2250366.VB8doyBIfi@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@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 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).