linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org,
	Stephen Warren <swarren@wwwdotorg.org>,
	linux-tegra@vger.kernel.org, Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH] pinctrl: tegra: move Tegra pinctrl drivers to sub-directory
Date: Mon, 25 Jan 2016 13:26:32 +0100	[thread overview]
Message-ID: <20160125122632.GC20452@ulmo.nvidia.com> (raw)
In-Reply-To: <1453563008-30106-1-git-send-email-yamada.masahiro@socionext.com>

[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]

On Sun, Jan 24, 2016 at 12:30:08AM +0900, Masahiro Yamada wrote:
> Tegra has several pinctrl drivers.  Now it is reasonable enough to
> move them into drivers/pinctrl/tegra/.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
> 
>  drivers/pinctrl/Kconfig                          | 32 +-----------------------
>  drivers/pinctrl/Makefile                         |  8 +-----
>  drivers/pinctrl/tegra/Kconfig                    | 30 ++++++++++++++++++++++
>  drivers/pinctrl/tegra/Makefile                   |  7 ++++++
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra-xusb.c |  4 +--
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra.c      |  4 +--
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra.h      |  0
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra114.c   |  0
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra124.c   |  0
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra20.c    |  0
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra210.c   |  0
>  drivers/pinctrl/{ => tegra}/pinctrl-tegra30.c    |  0
>  12 files changed, 43 insertions(+), 42 deletions(-)
>  create mode 100644 drivers/pinctrl/tegra/Kconfig
>  create mode 100644 drivers/pinctrl/tegra/Makefile
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra-xusb.c (99%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra.c (99%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra.h (100%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra114.c (100%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra124.c (100%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra20.c (100%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra210.c (100%)
>  rename drivers/pinctrl/{ => tegra}/pinctrl-tegra30.c (100%)

I'll leave it up to Linus to decide if this is worthwhile, I don't feel
strongly either way. If you want to go with this:

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-25 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 15:30 [PATCH] pinctrl: tegra: move Tegra pinctrl drivers to sub-directory Masahiro Yamada
2016-01-25 12:26 ` Thierry Reding [this message]
2016-02-05 14:17 ` 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=20160125122632.GC20452@ulmo.nvidia.com \
    --to=thierry.reding@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=yamada.masahiro@socionext.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).