From: Linus Walleij <linus.walleij@linaro.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
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] pinctrl: uniphier: widen all pinconf-derived arguments to u32
Date: Mon, 7 Aug 2017 15:10:50 +0200 [thread overview]
Message-ID: <CACRpkdYvZwQaoHEi0rC+OgSrk2gLjp4ibJvOBCVT0Ss2KVCLyQ@mail.gmail.com> (raw)
In-Reply-To: <1501819285-12827-1-git-send-email-yamada.masahiro@socionext.com>
On Fri, Aug 4, 2017 at 6:01 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> Since commit 58957d2edfa1 ("pinctrl: Widen the generic pinconf argument
> from 16 to 24 bits"), the generic pinconf arguments are handled by u32.
>
> UniPhier pinctrl drivers do not support debouncing, so u16 is working,
> but align the argument type to u32 for consistency.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Patch applied.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-08-07 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 4:01 [PATCH] pinctrl: uniphier: widen all pinconf-derived arguments to u32 Masahiro Yamada
2017-08-07 13:10 ` Linus Walleij [this message]
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=CACRpkdYvZwQaoHEi0rC+OgSrk2gLjp4ibJvOBCVT0Ss2KVCLyQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).