linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-sh@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] gpio: rcar: Remove obsolete platform data support
Date: Wed, 07 Oct 2015 08:23:42 +0000	[thread overview]
Message-ID: <1444206225-25664-1-git-send-email-geert+renesas@glider.be> (raw)

	Hi Greg, Linus, Alexandre,

Since commit 4baadb9e05c68962 ("ARM: shmobile: r8a7778: remove obsolete
setup code"), which is now in arm-soc/for-next, Renesas R-Car SoCs are
only supported in generic DT-only ARM multi-platform builds.  The driver
doesn't need to use platform data anymore, hence this driver removes
platform data configuration.

Unfortunately the platform data header file is used in a few other
places, so we have to fix these first to avoid breaking the build.

Thanks!

Geert Uytterhoeven (3):
  usb: renesas_usbhs: Remove unneeded #include
    <linux/platform_data/gpio-rcar.h>
  pinctrl: sh-pfc: Stop including <linux/platform_data/gpio-rcar.h>
  gpio: rcar: Remove obsolete platform data support

 drivers/gpio/gpio-rcar.c                | 77 +++++++++++----------------------
 drivers/pinctrl/sh-pfc/pfc-r8a7778.c    |  1 -
 drivers/pinctrl/sh-pfc/pfc-r8a7779.c    |  1 -
 drivers/pinctrl/sh-pfc/pfc-r8a7790.c    |  1 -
 drivers/pinctrl/sh-pfc/pfc-r8a7791.c    |  1 -
 drivers/pinctrl/sh-pfc/pfc-r8a7794.c    |  1 -
 drivers/pinctrl/sh-pfc/pfc-r8a7795.c    |  1 -
 drivers/pinctrl/sh-pfc/sh_pfc.h         |  5 +++
 drivers/usb/renesas_usbhs/rcar2.c       |  1 -
 include/linux/platform_data/gpio-rcar.h | 29 -------------
 10 files changed, 31 insertions(+), 87 deletions(-)
 delete mode 100644 include/linux/platform_data/gpio-rcar.h

-- 
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-10-07  8:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07  8:23 Geert Uytterhoeven [this message]
     [not found] ` <1444206225-25664-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-10-07  8:23   ` [PATCH 1/3] usb: renesas_usbhs: Remove unneeded #include <linux/platform_data/gpio-rcar.h> Geert Uytterhoeven
2015-10-07 10:33     ` Yoshihiro Shimoda
     [not found]     ` <1444206225-25664-2-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-10-17  6:33       ` Greg Kroah-Hartman
2015-10-19 14:21       ` Felipe Balbi
2015-10-07  8:23 ` [PATCH 2/3] pinctrl: sh-pfc: Stop including <linux/platform_data/gpio-rcar.h> Geert Uytterhoeven
2015-10-16 15:04   ` Linus Walleij
2015-10-07  8:23 ` [PATCH 3/3] gpio: rcar: Remove obsolete platform data support Geert Uytterhoeven
2015-10-16 15:05 ` [PATCH 0/3] " 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=1444206225-25664-1-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=gnurou@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-usb@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).