From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 1/2] pinctrl: sh-pfc: r8a7795: Fix hscif2_clk_b and hscif4_ctrl
Date: Thu, 16 Mar 2017 13:49:00 +0100 [thread overview]
Message-ID: <CAMuHMdWNYqNxcBHTNiTyDe3ZED0L07z4AhRiOcfNBj4QiMJ9Ag@mail.gmail.com> (raw)
In-Reply-To: <e5214bac-7bf9-1897-cf9f-f4735e6985e9@cogentembedded.com>
Hei Sergey,
On Mon, Mar 13, 2017 at 5:57 PM, Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> On 03/13/2017 07:41 PM, Geert Uytterhoeven wrote:
>
>> Fix typos in hscif2_clk_[bc]_mux[] and hscif4_ctrl_mux[].
>
> Only seeing hscif2_clk_b_mux[] fix...
Thanks for noticing, I had copied this line from another patch for r8a7796,
but forgot to update it.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-03-16 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 16:41 [PATCH 0/2] pinctrl: sh-pfc: r8a7795: Misc fixes and cleanups Geert Uytterhoeven
2017-03-13 16:41 ` [PATCH 1/2] pinctrl: sh-pfc: r8a7795: Fix hscif2_clk_b and hscif4_ctrl Geert Uytterhoeven
2017-03-13 16:57 ` Sergei Shtylyov
2017-03-16 12:49 ` Geert Uytterhoeven [this message]
2017-03-16 12:49 ` Geert Uytterhoeven
2017-03-13 16:41 ` [PATCH 2/2] pinctrl: sh-pfc: r8a7795: Restore sort order Geert Uytterhoeven
2017-03-15 10:26 ` [PATCH 0/2] pinctrl: sh-pfc: r8a7795: Misc fixes and cleanups Linus Walleij
2017-03-15 10:46 ` Geert Uytterhoeven
2017-03-22 13:25 ` 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=CAMuHMdWNYqNxcBHTNiTyDe3ZED0L07z4AhRiOcfNBj4QiMJ9Ag@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 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).