From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [RFC/PATCH v2 09/13] dt: omap4: add soc file for handling i2c controllers
Date: Tue, 23 Aug 2011 21:45:09 +0200 [thread overview]
Message-ID: <4E540345.1090004@ti.com> (raw)
In-Reply-To: <20110823151841.GB32698@manju-desktop>
On 8/23/2011 5:18 PM, G, Manjunath Kondaiah wrote:
> On Tue, Aug 23, 2011 at 03:48:15PM +0200, Cousson, Benoit wrote:
>> From: G, Manjunath Kondaiah<manjugk@ti.com>
>>> To: devicetree-discuss at lists.ozlabs.org
>>> CC: linux-omap at vger.kernel.org, linux-arm-kernel at lists.infradead.org
>>>
>>>
>>> Add omap4 soc dts file for handling omap4 soc i2c
>>> controllers existing on l4-core bus.
>>
>> The subject and changelog is not accurate. You are doing at least 3 things:
>> Moving the OMAP4 SoC data from panda board file to a SoC specific
>> omap4.dtsi file.
>> Including the omap4.dtsi into panda.
>> Adding some i2c nodes.
>>
>> You should use at least two or three separated patches to avoid
>> in-accurate subject.
>
> As these changes are straight forward, I can update patch description with
> the required information instead of create too many patches.
>
> If you are too specific on splitting the patches, I am ok with that too.
I already fixed partially the OMAP4 patches as part of my upcoming OMAP4
early devices DT migration. So I'll rebase your series on top of it.
I'll send you that tomorrow.
Benoit
next prev parent reply other threads:[~2011-08-23 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1314074021-25186-1-git-send-email-manjugk@ti.com>
[not found] ` <1314074021-25186-10-git-send-email-manjugk@ti.com>
2011-08-23 8:23 ` [RFC/PATCH v2 09/13] dt: omap4: add soc file for handling i2c controllers Rajendra Nayak
2011-08-23 15:11 ` G, Manjunath Kondaiah
[not found] ` <4E537FA7.3050609@ti.com>
2011-08-23 13:48 ` Fwd: " Cousson, Benoit
2011-08-23 15:18 ` G, Manjunath Kondaiah
2011-08-23 19:45 ` Cousson, Benoit [this message]
[not found] ` <1314074021-25186-8-git-send-email-manjugk@ti.com>
2011-08-23 9:07 ` [RFC/PATCH v2 07/13] dt: omap: create platform bus for omap devices Jamie Iles
2011-08-23 15:19 ` G, Manjunath Kondaiah
[not found] ` <4E537ECB.1060704@ti.com>
2011-08-23 12:38 ` [RFC/PATCH v2 00/13] dt: omap: dt binding with omap_device and support for i2c1 Cousson, Benoit
2011-08-23 15:41 ` G, Manjunath Kondaiah
2011-08-24 9:41 ` Cousson, Benoit
[not found] ` <1314074021-25186-9-git-send-email-manjugk@ti.com>
2011-08-23 15:46 ` [RFC/PATCH v2 08/13] dt: omap: i2c: add dt support for i2c1 controller G, Manjunath Kondaiah
2011-09-01 17:34 ` Cousson, Benoit
2011-09-02 3:22 ` G, Manjunath Kondaiah
[not found] ` <4E537F53.4030405@ti.com>
2011-08-23 19:15 ` Fwd: " Cousson, Benoit
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=4E540345.1090004@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).