linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/4] pinctrl: sh-pfc: More PINMUX_SINGLE() conversions
Date: Mon, 30 Nov 2015 14:41:01 +0100	[thread overview]
Message-ID: <1448890865-1856-1-git-send-email-geert+renesas@glider.be> (raw)

	Hi Laurent, Linus,

This patch series converts pin control data for a few more Renesas SoCs
to the recently-introduced PINMUX_SINGLE() macro.
As such this series depends on "[PATCH/RFC 0/4] pinctrl: sh-pfc: Add
PINMUX_SINGLE()".

Thanks!

Geert Uytterhoeven (4):
  pinctrl: sh-pfc: emev2: Use PINMUX_SINGLE() instead of raw
    PINMUX_DATA()
  pinctrl: sh-pfc: r8a7778: Use PINMUX_SINGLE() instead of raw
    PINMUX_DATA()
  pinctrl: sh-pfc: r8a7779: Use PINMUX_SINGLE() instead of raw
    PINMUX_DATA()
  pinctrl: sh-pfc: sh7734: Use PINMUX_SINGLE() instead of raw
    PINMUX_DATA()

 drivers/pinctrl/sh-pfc/pfc-emev2.c   | 134 +++++++++++++++++------------------
 drivers/pinctrl/sh-pfc/pfc-r8a7778.c |  22 +++---
 drivers/pinctrl/sh-pfc/pfc-r8a7779.c |  16 ++---
 drivers/pinctrl/sh-pfc/pfc-sh7734.c  |  21 +++---
 4 files changed, 98 insertions(+), 95 deletions(-)

-- 
1.9.1

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

             reply	other threads:[~2015-11-30 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 13:41 Geert Uytterhoeven [this message]
2015-11-30 13:41 ` [PATCH 1/4] pinctrl: sh-pfc: emev2: Use PINMUX_SINGLE() instead of raw PINMUX_DATA() Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 2/4] pinctrl: sh-pfc: r8a7778: " Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 3/4] pinctrl: sh-pfc: r8a7779: " Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 4/4] pinctrl: sh-pfc: sh7734: " Geert Uytterhoeven
2016-02-04 18:51 ` [PATCH 0/4] pinctrl: sh-pfc: More PINMUX_SINGLE() conversions Laurent Pinchart
2016-02-15 18:26 ` Linus Walleij
2016-02-15 18:39   ` Geert Uytterhoeven
2016-02-16 15:19     ` 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=1448890865-1856-1-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --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 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).