From: Benoit Cousson <bcousson@baylibre.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, uri.y@variscite.com, nm@ti.com
Subject: Re: [PATCH v2 0/2] omap4/twl6030: typical connection to omap4 as a separate dtsi file
Date: Wed, 14 Aug 2013 15:51:01 +0200 [thread overview]
Message-ID: <520B8B45.1010300@baylibre.com> (raw)
In-Reply-To: <1376469348-10797-1-git-send-email-ruslan.bilovol@ti.com>
Hi Ruslan,
On 14/08/2013 10:35, Ruslan Bilovol wrote:
> Hello,
>
> There is no functional changes between v1 and v2 - just
> added the patch for omap4-var-som - Uri Yosef confirmed
> this board have the same connection of OMAP4<->TWL6030 as
> SDP4430 board
The series looks good to me, but it will be good to have a test for
Panda and Variscite boards before merging it.
Regards,
Benoit
next prev parent reply other threads:[~2013-08-14 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 8:35 [PATCH v2 0/2] omap4/twl6030: typical connection to omap4 as a separate dtsi file Ruslan Bilovol
2013-08-14 8:35 ` [PATCH v2 1/2] arm: dts: twl6030: " Ruslan Bilovol
2013-08-14 8:35 ` [PATCH v2 2/2] arm: dts: omap4: configure connection to PMIC on Variscite's SOM Ruslan Bilovol
2013-08-14 13:51 ` Benoit Cousson [this message]
2013-08-16 12:04 ` [PATCH v2 0/2] omap4/twl6030: typical connection to omap4 as a separate dtsi file Ruslan Bilovol
[not found] ` <CAHooxd7Sg8B-MM38F2ce=vR5ftO6ye2byrXH1-iFous=_AvTLg@mail.gmail.com>
2013-08-16 13:17 ` Benoit Cousson
2013-08-16 13:20 ` Benoit Cousson
2013-08-19 6:14 ` Ruslan Bilovol
2013-08-19 10:04 ` Benoit Cousson
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=520B8B45.1010300@baylibre.com \
--to=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=ruslan.bilovol@ti.com \
--cc=uri.y@variscite.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox