From: Grant Likely <grant.likely@secretlab.ca>
To: Doug Anderson <dianders@chromium.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Thomas Abraham <thomas.abraham@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Kukjin Kim <kgene.kim@samsung.com>,
heiko@sntech.de, Jaswinder Singh <jaswinder.singh@linaro.org>,
Tomasz Figa <t.figa@samsung.com>,
linux-samsung-soc@vger.kernel.org,
spi-devel-general@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org,
Doug Anderson <dianders@chromium.org>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>, Ben Dooks <ben-linux@fluff.org>,
Mark Brown <broonie@kernel.org>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [REPOST PATCH] spi: s3c64xx: let device core setup the default pin configuration
Date: Tue, 16 Apr 2013 11:24:02 +0100 [thread overview]
Message-ID: <20130416102402.DF3493E14C0@localhost> (raw)
In-Reply-To: <1366083777-9118-1-git-send-email-dianders@chromium.org>
On Mon, 15 Apr 2013 20:42:57 -0700, Doug Anderson <dianders@chromium.org> wrote:
> From: Thomas Abraham <thomas.abraham@linaro.org>
>
> With device core now able to setup the default pin configuration,
> the pin configuration code based on the deprecated Samsung specific
> gpio bindings is removed.
>
> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> Signed-off-by: Doug Anderson <dianders@chromium.org>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
> Tested-by: Doug Anderson <dianders@chromium.org>
Applied, thanks.
g.
prev parent reply other threads:[~2013-04-16 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:42 [PATCH] spi: s3c64xx: let device core setup the default pin configuration Thomas Abraham
2013-03-07 8:11 ` Linus Walleij
2013-03-11 17:36 ` Doug Anderson
2013-04-15 17:23 ` Doug Anderson
2013-04-15 18:27 ` Linus Walleij
2013-04-16 3:42 ` [REPOST PATCH] " Doug Anderson
2013-04-16 10:24 ` Grant Likely [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=20130416102402.DF3493E14C0@localhost \
--to=grant.likely@secretlab.ca \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=jaswinder.singh@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=t.figa@samsung.com \
--cc=thomas.abraham@linaro.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).