From: Felipe Balbi <balbi@ti.com>
To: Afzal Mohammed <afzal@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Lokesh Vutla <lokeshvutla@ti.com>,
Sourav Poddar <sourav.poddar@ti.com>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Landley <rob@landley.net>,
Russell King <linux@arm.linux.org.uk>,
Benoit Cousson <bcousson@baylibre.com>,
Rajendra Nayak <rnayak@ti.com>
Subject: Re: [PATCH] ARM: dts: AM437x GP EVM support
Date: Tue, 12 Nov 2013 08:22:06 -0600 [thread overview]
Message-ID: <20131112142206.GD31721@saruman.home> (raw)
In-Reply-To: <1384255468-2453-1-git-send-email-afzal@ti.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Hi,
On Tue, Nov 12, 2013 at 04:54:26PM +0530, Afzal Mohammed wrote:
> From: Lokesh Vutla <lokeshvutla@ti.com>
>
> AM437x GP EVM DTS with pinmux information to make I2C on EVM usable.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
> Signed-off-by: Afzal Mohammed <afzal@ti.com>
could you instead send the much more complete version we already have
at [1] ? It's pointless to repatch all of that in this file if we *know*
those are already working.
[1] http://git.ti.com/cgit/cgit.cgi/ti-linux-kernel/ti-linux-kernel.git/tree/arch/arm/boot/dts/am437x-gp-evm.dts?h=ti-linux-3.12.y
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-12 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 11:24 [PATCH] ARM: dts: AM437x GP EVM support Afzal Mohammed
2013-11-12 14:22 ` Felipe Balbi [this message]
2013-11-13 7:04 ` Afzal Mohammed
2013-11-13 12:44 ` Felipe Balbi
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=20131112142206.GD31721@saruman.home \
--to=balbi@ti.com \
--cc=afzal@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lokeshvutla@ti.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sourav.poddar@ti.com \
--cc=swarren@wwwdotorg.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).