All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: [GIT PULL] ARM: OMAP: i2c, gpio, spi and regulator DTS updates
Date: Thu, 15 Mar 2012 00:04:04 +0100	[thread overview]
Message-ID: <4F6123E4.5090808@ti.com> (raw)
In-Reply-To: <20120314225743.GT12083@atomide.com>

On 3/14/2012 11:57 PM, Tony Lindgren wrote:
> * Cousson, Benoit<b-cousson@ti.com>  [120314 15:52]:
>> Hi Tony,
>>
>> It looks like Chris Ball just queued  the HSMMC DT stuff from
>> Rajendra, so I can add as well the MMC DTS for OMAP3 and OMAP4 as
>> well.
>>
>> It is fine for an update?
>
> Sure, I'm not planning to pull this until after the merge
> window.

OK, so we will not have the DTS support for the new drivers for 3.4 :-(

Well, if you pull that in a lo branch, that will be enough to base the 
further work on it.

>> Than I can add as Kevin's patch for twl irq_base removal.
>
> Hmm I don't follow. That's needed first as a fix for the
> merge window?

No, not that one. It is just some more cleanup on top of the one Felipe 
already did in the twl series I've just sent to Samuel.
But if you do not plan to pull that series for 3.4, that does not really 
matter.

Regards,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: i2c, gpio, spi and regulator DTS updates
Date: Thu, 15 Mar 2012 00:04:04 +0100	[thread overview]
Message-ID: <4F6123E4.5090808@ti.com> (raw)
In-Reply-To: <20120314225743.GT12083@atomide.com>

On 3/14/2012 11:57 PM, Tony Lindgren wrote:
> * Cousson, Benoit<b-cousson@ti.com>  [120314 15:52]:
>> Hi Tony,
>>
>> It looks like Chris Ball just queued  the HSMMC DT stuff from
>> Rajendra, so I can add as well the MMC DTS for OMAP3 and OMAP4 as
>> well.
>>
>> It is fine for an update?
>
> Sure, I'm not planning to pull this until after the merge
> window.

OK, so we will not have the DTS support for the new drivers for 3.4 :-(

Well, if you pull that in a lo branch, that will be enough to base the 
further work on it.

>> Than I can add as Kevin's patch for twl irq_base removal.
>
> Hmm I don't follow. That's needed first as a fix for the
> merge window?

No, not that one. It is just some more cleanup on top of the one Felipe 
already did in the twl series I've just sent to Samuel.
But if you do not plan to pull that series for 3.4, that does not really 
matter.

Regards,
Benoit

  reply	other threads:[~2012-03-14 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 23:41 [GIT PULL] ARM: OMAP: i2c, gpio, spi and regulator DTS updates Cousson, Benoit
2012-03-12 23:41 ` Cousson, Benoit
2012-03-14 22:50 ` Cousson, Benoit
2012-03-14 22:50   ` Cousson, Benoit
2012-03-14 22:57   ` Tony Lindgren
2012-03-14 22:57     ` Tony Lindgren
2012-03-14 23:04     ` Cousson, Benoit [this message]
2012-03-14 23:04       ` Cousson, Benoit
2012-03-14 23:21       ` Tony Lindgren
2012-03-14 23:21         ` Tony Lindgren
2012-03-14 23:38         ` Cousson, Benoit
2012-03-14 23:38           ` 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=4F6123E4.5090808@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.