From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>, linus.walleij@linaro.org
Cc: rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
rob@landley.net, thierry.reding@gmail.com,
grant.likely@linaro.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/2] pinctrl: tegra: Add devicetree binding document for Tegra124
Date: Thu, 12 Dec 2013 11:39:41 -0700 [thread overview]
Message-ID: <52AA02ED.90309@wwwdotorg.org> (raw)
In-Reply-To: <1386659456-16887-1-git-send-email-ldewangan@nvidia.com>
On 12/10/2013 12:10 AM, Laxman Dewangan wrote:
> This device tree binding document describes the Tegra124 pincontrol
> DT bindings. This document lists all valid properties, names, mux
> options of Tegra124 pins.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> Acked-by: Stephen Warren <swarren@nvidia.com>
Just to be clear: My acks on this series are valid, and I think this
series should be merged.
next prev parent reply other threads:[~2013-12-12 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 7:10 [PATCH V3 1/2] pinctrl: tegra: Add devicetree binding document for Tegra124 Laxman Dewangan
2013-12-10 7:10 ` Laxman Dewangan
2013-12-10 7:10 ` [PATCH V3 2/2] pinctrl: tegra: add pinmux controller driver " Laxman Dewangan
2013-12-10 7:10 ` Laxman Dewangan
[not found] ` <1386659456-16887-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-12 21:30 ` Linus Walleij
2013-12-12 21:30 ` Linus Walleij
2013-12-12 18:39 ` Stephen Warren [this message]
[not found] ` <1386659456-16887-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-12 21:26 ` [PATCH V3 1/2] pinctrl: tegra: Add devicetree binding document " Linus Walleij
2013-12-12 21:26 ` Linus Walleij
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=52AA02ED.90309@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.