From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: uniphier: guard uniphier directory with CONFIG_PINCTRL_UNIPHIER
Date: Fri, 30 Oct 2015 19:29:26 +0900 [thread overview]
Message-ID: <CAK7LNAQsD=kG1X0SXPJ78FLpgEwk023cHEjE8P2UAAPhFATqOg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZ286dBTvd3EO_GTixnS=Cz-ch-H+AzNOJhZwoB63K6jw@mail.gmail.com>
Hi Linus.
2015-10-29 22:34 GMT+09:00 Linus Walleij <linus.walleij@linaro.org>:
> On Tue, Oct 27, 2015 at 3:28 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>
>> CONFIG_PINCTRL_UNIPHIER is more suitable than CONFIG_ARCH_UNIPHIER
>> to guard the drivers/pinctrl/uniphier directory.
>>
>> The current CONFIG_PINCTRL_UNIPHIER_CORE is a bit long
>> (it would break the indentation in drivers/pinctrl/Makefile),
>> so rename it into CONFIG_PINCTRL_UNIPHIER.
>>
>> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>
> Holding this back until we know what to do with the first patch
> but it looks OK.
I've re-sent this as a single patch
in case 1/2 might take some time for review.
As you agreed with this one, please let it go in first.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2015-10-30 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 2:28 [PATCH 1/2] pinctrl: uniphier: enable UniPhier SoCs pinctrl drivers by default Masahiro Yamada
2015-10-27 2:28 ` [PATCH 2/2] pinctrl: uniphier: guard uniphier directory with CONFIG_PINCTRL_UNIPHIER Masahiro Yamada
2015-10-29 13:34 ` Linus Walleij
2015-10-30 10:29 ` Masahiro Yamada [this message]
2015-10-29 13:33 ` [PATCH 1/2] pinctrl: uniphier: enable UniPhier SoCs pinctrl drivers by default Linus Walleij
2015-10-30 2:01 ` Masahiro Yamada
2015-10-31 1:41 ` Olof Johansson
2015-11-02 11:47 ` Masahiro Yamada
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='CAK7LNAQsD=kG1X0SXPJ78FLpgEwk023cHEjE8P2UAAPhFATqOg@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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).