From: Simon Horman <horms@verge.net.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH/RESEND 1/2] gpio: rcar: Remove #gpio-range-cells DT property usage
Date: Fri, 20 Sep 2013 12:06:14 -0700 [thread overview]
Message-ID: <20130920190614.GF22321@verge.net.au> (raw)
In-Reply-To: <CACRpkdZ4EaUVgYoMP6VMefZgE1T--5hh18RzupQLnbd0KpveAA@mail.gmail.com>
On Fri, Sep 20, 2013 at 08:36:57PM +0200, Linus Walleij wrote:
> On Wed, Sep 11, 2013 at 3:51 PM, Laurent Pinchart
> <laurent.pinchart+renesas@ideasonboard.com> wrote:
>
> > Commit a1bc260bb5f5d95da854be7898202d788e94448d ("gpio: clean up
> > gpio-ranges documentation") deprecated the #gpio-range-cells property.
> > Replace its usage with a hardcoded value in the gpio-rcar driver.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Simon please take the whole set into the SH tree.
Thanks, will do.
next prev parent reply other threads:[~2013-09-20 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 13:51 [PATCH/RESEND 0/2] ARM: shmobile: Remove #gpio-ranges-cells property Laurent Pinchart
2013-09-11 13:51 ` [PATCH/RESEND 1/2] gpio: rcar: Remove #gpio-range-cells DT property usage Laurent Pinchart
2013-09-20 18:36 ` Linus Walleij
2013-09-20 19:06 ` Simon Horman [this message]
2013-09-20 19:57 ` Laurent Pinchart
2013-09-22 12:04 ` Simon Horman
2013-09-22 12:27 ` Simon Horman
2013-09-11 13:51 ` [PATCH/RESEND 2/2] ARM: shmobile: Remove #gpio-ranges-cells DT property Laurent Pinchart
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=20130920190614.GF22321@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).