From: Shawn Guo <shawn.guo@linaro.org>
To: Stefan Agner <stefan@agner.ch>
Cc: kernel@pengutronix.de, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: vf610: remove unused gpio-range-cells property
Date: Tue, 3 Mar 2015 12:13:31 +0800 [thread overview]
Message-ID: <20150303041329.GN20455@dragon> (raw)
In-Reply-To: <1425311881-10767-1-git-send-email-stefan@agner.ch>
On Mon, Mar 02, 2015 at 04:58:01PM +0100, Stefan Agner wrote:
> The anyway depricated gpio-range-cells property was never used
> by the pin controller driver. This patch removes it.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
prev parent reply other threads:[~2015-03-03 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 15:58 [PATCH] ARM: dts: vf610: remove unused gpio-range-cells property Stefan Agner
2015-03-03 4:13 ` Shawn Guo [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=20150303041329.GN20455@dragon \
--to=shawn.guo@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@agner.ch \
/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).