From: Sourav Poddar <sourav.poddar@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, balbi@ti.com,
santosh.shilimkar@ti.com, Andrew Morton <akpm@osdl.org>
Subject: Re: [Resend/PATCH 0/5] omap4/5: i2c/spi: device tree data
Date: Mon, 11 Mar 2013 21:12:26 +0530 [thread overview]
Message-ID: <513DFB62.5030709@ti.com> (raw)
In-Reply-To: <513DEAE1.1050606@ti.com>
On Monday 11 March 2013 08:02 PM, Benoit Cousson wrote:
> Hi Sourav,
>
> On 03/11/2013 02:44 PM, Sourav Poddar wrote:
>> Hi Tony/Benoit,
>>
>> These patches had been sent couple of times before, but there were no comments on it.
> Sorry for that. I got a big flu in Jan and was in Linaro Connect last week.
> Patches look good, I just have to check that they apply nicely to the
> dts/for_3.9 I already prepared.
>
Ok. Thanks!!
> I still have to rebase that branch on top of a recent master branch and
> then check your branch.
>
>> If there are no comments, Can these be picked ?
>> Cc: Andrew Morton<akpm@osdl.org>
>>
>> The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
>>
>> Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
>>
>> are available in the git repository at:
>> git@gitorious.org:linux-connectivity/linux-connectivity.git omap_i2c_spi_dts_data
>>
>> Felipe Balbi (1):
>> arm: dts: omap5: add SPI devices to OMAP5 DeviceTree file
>>
>> Sourav Poddar (4):
>> arm: dts: omap4-sdp: Add I2c pinctrl data
>> arm: dts: omap5-evm: Add I2c pinctrl data
>> arm: dts: omap4-panda: Add I2c pinctrl data
>> arm: dts: omap5-evm: Add mcspi data
> Thanks,
> Benoit
>
next prev parent reply other threads:[~2013-03-11 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 13:44 [Resend/PATCH 0/5] omap4/5: i2c/spi: device tree data Sourav Poddar
2013-03-11 14:32 ` Benoit Cousson
2013-03-11 15:42 ` Sourav Poddar [this message]
2013-03-13 16:46 ` Benoit Cousson
2013-03-13 18:07 ` Sourav Poddar
2013-03-14 6:10 ` 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=513DFB62.5030709@ti.com \
--to=sourav.poddar@ti.com \
--cc=akpm@osdl.org \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).