linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>, "Cousson, Benoit" <b-cousson@ti.com>,
	Paul Walmsley <paul@pwsan.com>,
	Jarkko Nikula <jhnikula@gmail.com>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] USB patches for next merge window
Date: Tue, 24 May 2011 13:04:56 +0300	[thread overview]
Message-ID: <20110524100455.GA14371@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20110524085244.GE30799@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

Hi,

On Tue, May 24, 2011 at 11:52:45AM +0300, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [110523 11:11]:
> > On Mon, May 23, 2011 at 10:15:15AM +0300, Jarkko Nikula wrote:
> > > On Mon, 23 May 2011 09:14:38 +0300
> > > Felipe Balbi <balbi@ti.com> wrote:
> > > 
> > > > a gentle ping here too. Without this we will have regressions on
> > > > ehci/ohci as the pm_runtime patches have gone in via Samuel.
> > > > 
> > > Does this mean that those regressions happened already when those
> > > patches were made if there is pull request dependency?
> > 
> > not really, no.
> > 
> > > Remember bisectability is important. And very important if you are
> > > bisecting something else but which is dependent on this as then you
> > > could mark wrong good/bad points or not able to determine.
> > 
> > True, true... I just wanted to avoid conflicts as much as possible so
> > arch/arm/*omap*/ goes through Tony, and drivers/mfd/* goes through
> > Samuel.
> > 
> > pm_rutime and hwmod conversion aren't really that tightly coupled. As
> > long as the arch code is in place, we can do pm_runtime at any time. Not
> > sure if it's true the other way around. But one thing is for sure, if
> > this pull request isn't taken, then I guess clocks won't enable on
> > omap-usbhs...
> 
> Looks like these patches are missing acks from Benoit and Paul?
> I'd rather not pull them in without the acks. Note that we have
> a very short merge window this time, so let's see if we can still
> get them in.

Ok... let's see if they'll Ack the patches which have been floating
around. [1], [2] and [3] are the patches which need Ack.

[1] http://marc.info/?l=linux-omap&m=130512838504191&w=2
[2] http://marc.info/?l=linux-omap&m=130512862104681&w=2
[3] http://marc.info/?l=linux-omap&m=130512812503806&w=2

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-05-24 10:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110518110353.GH13908@legolas.emea.dhcp.ti.com>
2011-05-18 11:42 ` [GIT PULL] USB patches for next merge window Felipe Balbi
2011-05-23  6:14   ` Felipe Balbi
2011-05-23  7:15     ` Jarkko Nikula
2011-05-23  8:15       ` Felipe Balbi
2011-05-24  8:52         ` Tony Lindgren
2011-05-24 10:04           ` Felipe Balbi [this message]
2011-05-24 12:14             ` 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=20110524100455.GA14371@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=b-cousson@ti.com \
    --cc=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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).