linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.or,
	tony@atomide.com
Subject: Re: [PATCH 0/5] ARM: OMAP: Few device tree patches for 3.7
Date: Mon, 3 Sep 2012 17:04:03 +0200	[thread overview]
Message-ID: <5044C6E3.10304@ti.com> (raw)
In-Reply-To: <5035DC7C.2000105@ti.com>

Hi Santosh,

Sorry for the delay, I missed that email :-(

On 08/23/2012 09:32 AM, Santosh Shilimkar wrote:
> Benoit,
> 
> On Monday 13 August 2012 04:30 PM, Santosh Shilimkar wrote:
>> These are the few device tree related patches which has been posted and
>> reviewed on the list. They are intended for 3.7 merge window but I am
>> posting them early enough to get into linux-next and linux-omap for
>> testing.
>>
>> The following changes since commit
>> 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
>>
>>    Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
>>
>> are available in the git repository at:
>>
>>    git://github.com/SantoshShilimkar/linux.git for_3.7/omap_dt
>>
>> for you to fetch changes up to bedee5fcb18062dfc933e0971e67fd6889c6446d:
>>
>>    ARM: OMAP4: Add local timer support for Device Tree (2012-08-13
>> 11:59:26 +0530)
>>
>> ----------------------------------------------------------------
>> Aneesh V (3):
>>        dt: device tree bindings for LPDDR2 memories
>>        dt: emif: device tree bindings for TI's EMIF sdram controller
>>        ARM: dts: EMIF and LPDDR2 device tree data for OMAP4 boards
>>
>> Santosh Shilimkar (2):
>>        ARM: OMAP4: Add L2 Cache Controller in Device Tree
>>        ARM: OMAP4: Add local timer support for Device Tree
>>
> 
> Will you pull this series from above git url or do you want me to send
> a separate git pull request email ?

I'll merge that branch on top of Sourav's and Peter's series and send
the pull request to Tony.

Regards,
Benoit


  reply	other threads:[~2012-09-03 15:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 11:00 [PATCH 0/5] ARM: OMAP: Few device tree patches for 3.7 Santosh Shilimkar
2012-08-13 11:00 ` [PATCH 1/5] dt: device tree bindings for LPDDR2 memories Santosh Shilimkar
2012-08-13 11:00 ` [PATCH 2/5] dt: emif: device tree bindings for TI's EMIF sdram controller Santosh Shilimkar
2012-08-13 11:00 ` [PATCH 3/5] ARM: dts: EMIF and LPDDR2 device tree data for OMAP4 boards Santosh Shilimkar
2012-08-13 11:00 ` [PATCH 4/5] ARM: OMAP4: Add L2 Cache Controller in Device Tree Santosh Shilimkar
2012-08-20 13:51   ` Benoit Cousson
2012-08-20 15:51     ` Shilimkar, Santosh
2012-08-21  9:41       ` Shilimkar, Santosh
2012-08-21 10:24         ` Felipe Balbi
2012-08-21 10:32           ` Shilimkar, Santosh
2012-08-21 10:29             ` Felipe Balbi
2012-08-21 10:44             ` Benoit Cousson
2012-08-21 10:46               ` Shilimkar, Santosh
2012-08-20 15:59     ` Felipe Balbi
2012-08-13 11:00 ` [PATCH 5/5] ARM: OMAP4: Add local timer support for " Santosh Shilimkar
2012-08-23  7:32 ` [PATCH 0/5] ARM: OMAP: Few device tree patches for 3.7 Santosh Shilimkar
2012-09-03 15:04   ` Benoit Cousson [this message]
2012-09-04  5:24     ` Shilimkar, Santosh

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=5044C6E3.10304@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.or \
    --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).