From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: sh-pfc: r8a7795: Remove bits SEL_VSP_1 and SEL_VSP_0
Date: Wed, 27 Jan 2016 09:53:23 +0000 [thread overview]
Message-ID: <CACRpkdaqiYmTOVV3f5PEGyihuH+CRieNhCGfBWi7Lg3MBhC05g@mail.gmail.com> (raw)
In-Reply-To: <1452856024-10793-3-git-send-email-geert+renesas@glider.be>
On Fri, Jan 15, 2016 at 12:07 PM, Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Cfr. Manual Errata for Rev 0.50 of the R-Car Gen3 datasheet.
>
> This has no user-visible impact, as the definitions were not really
> used.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
I guess there will still be a huge influx of SH-PFC patches so we should
keep running pull request from you to me for the v4.6 kernel cycle.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: sh-pfc: r8a7795: Remove bits SEL_VSP_1 and SEL_VSP_0
Date: Wed, 27 Jan 2016 10:53:23 +0100 [thread overview]
Message-ID: <CACRpkdaqiYmTOVV3f5PEGyihuH+CRieNhCGfBWi7Lg3MBhC05g@mail.gmail.com> (raw)
In-Reply-To: <1452856024-10793-3-git-send-email-geert+renesas@glider.be>
On Fri, Jan 15, 2016 at 12:07 PM, Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Cfr. Manual Errata for Rev 0.50 of the R-Car Gen3 datasheet.
>
> This has no user-visible impact, as the definitions were not really
> used.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
I guess there will still be a huge influx of SH-PFC patches so we should
keep running pull request from you to me for the v4.6 kernel cycle.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-01-27 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 11:07 [PATCH 0/2] pinctrl: sh-pfc: r8a7795: Errata for Rev 0.50 datasheet Geert Uytterhoeven
2016-01-15 11:07 ` Geert Uytterhoeven
2016-01-15 11:07 ` [PATCH 1/2] pinctrl: sh-pfc: r8a7795: Rename SSI_{WS,SCK}0129 to SSI_{WS,SCK}01239 Geert Uytterhoeven
2016-01-15 11:07 ` Geert Uytterhoeven
2016-01-20 13:04 ` Linus Walleij
2016-01-20 13:04 ` Linus Walleij
2016-01-20 13:17 ` Geert Uytterhoeven
2016-01-20 13:17 ` Geert Uytterhoeven
2016-01-27 14:09 ` Linus Walleij
2016-01-27 14:09 ` Linus Walleij
2016-01-15 11:07 ` [PATCH 2/2] pinctrl: sh-pfc: r8a7795: Remove bits SEL_VSP_1 and SEL_VSP_0 Geert Uytterhoeven
2016-01-15 11:07 ` Geert Uytterhoeven
2016-01-27 9:53 ` Linus Walleij [this message]
2016-01-27 9:53 ` Linus Walleij
2016-01-15 23:15 ` [PATCH 0/2] pinctrl: sh-pfc: r8a7795: Errata for Rev 0.50 datasheet Laurent Pinchart
2016-01-15 23:15 ` Laurent Pinchart
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=CACRpkdaqiYmTOVV3f5PEGyihuH+CRieNhCGfBWi7Lg3MBhC05g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--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 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.