From: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
To: "Strashko, Grygorii" <grygorii.strashko-l0cyMroinI0@public.gmane.org>
Cc: "ivan.khoronzhuk-hExfYMNmJl/Cnp4W7fqMDg@public.gmane.org"
<ivan.khoronzhuk-hExfYMNmJl/Cnp4W7fqMDg@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2 0/2] ARM: dts: keystone: i2c updates
Date: Tue, 8 Apr 2014 09:16:17 -0400 [thread overview]
Message-ID: <5343F6A1.6010608@ti.com> (raw)
In-Reply-To: <1396957567-14540-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
On Tuesday 08 April 2014 07:46 AM, Strashko, Grygorii wrote:
> Hi Santosh,
>
> There are two small non critical fixes for Keystone 2 I2C DT definitions.
>
> Changes in v2;
> - added additional patch to move i2c0 device node from SoC to board files
> - updated commits messages
>
Thanks. I shall pick these up for 3.16.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-04-08 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 11:46 [PATCH v2 0/2] ARM: dts: keystone: i2c updates Grygorii Strashko
[not found] ` <1396957567-14540-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-04-08 11:46 ` [PATCH v2 1/2] ARM: dts: keystone: add cell's information to i2c nodes Grygorii Strashko
2014-04-08 11:46 ` [PATCH v2 2/2] ARM: dts: keystone: move i2c0 device node from SoC to board files Grygorii Strashko
2014-04-08 13:16 ` Santosh Shilimkar [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=5343F6A1.6010608@ti.com \
--to=santosh.shilimkar-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
--cc=ivan.khoronzhuk-hExfYMNmJl/Cnp4W7fqMDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).