From: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
To: santosh.shilimkar-l0cyMroinI0@public.gmane.org
Cc: ivan.khoronzhuk-hExfYMNmJl/Cnp4W7fqMDg@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Grygorii Strashko
<grygorii.strashko-l0cyMroinI0@public.gmane.org>
Subject: [PATCH v2 0/2] ARM: dts: keystone: i2c updates
Date: Tue, 8 Apr 2014 14:46:05 +0300 [thread overview]
Message-ID: <1396957567-14540-1-git-send-email-grygorii.strashko@ti.com> (raw)
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
Grygorii Strashko (2):
ARM: dts: keystone: add cell's information to i2c nodes
ARM: dts: keystone: move i2c0 device node from SoC to board files
arch/arm/boot/dts/k2e-evm.dts | 7 +++++++
arch/arm/boot/dts/k2hk-evm.dts | 7 +++++++
arch/arm/boot/dts/k2l-evm.dts | 7 +++++++
arch/arm/boot/dts/keystone.dtsi | 9 ++++-----
4 files changed, 25 insertions(+), 5 deletions(-)
--
1.7.9.5
--
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
next reply other threads:[~2014-04-08 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 11:46 Grygorii Strashko [this message]
[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 ` [PATCH v2 0/2] ARM: dts: keystone: i2c updates Santosh Shilimkar
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=1396957567-14540-1-git-send-email-grygorii.strashko@ti.com \
--to=grygorii.strashko-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ivan.khoronzhuk-hExfYMNmJl/Cnp4W7fqMDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@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).