public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: balbi@ti.com, Alan Stern <stern@rowland.harvard.edu>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Keshava Munegowda <Keshava_mgowda@ti.com>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: USB: fix warning on EHCI PHY reset path
Date: Mon, 7 May 2012 10:09:07 +0200	[thread overview]
Message-ID: <20120507080907.GB3229@sortiz-mobl> (raw)
In-Reply-To: <4FA61941.5080603@compulab.co.il>

Hi Igor,

On Sun, May 06, 2012 at 09:25:05AM +0300, Igor Grinberg wrote:
> Sorry, for being jumpy...
> Samuel has not answered yet (it has been more then two weeks already)
Sorry about that.

> and I'd like this to go into 3.5.
Then you may need a better changelog explaining how this fixes a regression,
runtime crash or build failure.


> Also, the dependency patch is already in Linus' tree. It has been merged with
> fixes (I thought it will happen only during the merge window...).
> 
> Can you, please take this one?
At that point, it definitely makes more sense for Alan to push it.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2012-05-07  8:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 14:08 [PATCH] ARM: OMAP: USB: fix warning on EHCI PHY reset path Igor Grinberg
2012-03-28  8:52 ` Felipe Balbi
2012-03-28 10:53   ` Raja, Govindraj
     [not found]     ` <CAMrsUdJjwAN4haHOkrGfrpb9HnbsMLyUE4a5aLnCPKC2JdUt_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-28 11:33       ` Igor Grinberg
2012-03-28 12:01     ` Munegowda, Keshava
     [not found] ` <4F72E1F9.3020400@ti.com>
2012-03-28 11:13   ` Igor Grinberg
2012-03-28 13:04     ` Shubhrajyoti Datta
2012-04-19 14:10 ` Igor Grinberg
     [not found]   ` <4F901CCC.9000703-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-04-19 15:01     ` Alan Stern
2012-04-20 11:57       ` Felipe Balbi
2012-05-06  6:25         ` Igor Grinberg
2012-05-07  8:09           ` Samuel Ortiz [this message]
2012-05-07 11:46             ` Igor Grinberg
     [not found]               ` <4FA7B61B.3020604-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-07 12:17                 ` Samuel Ortiz
     [not found]           ` <4FA61941.5080603-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-07 14:04             ` Alan Stern
2012-05-07 14:27               ` Igor Grinberg
     [not found]                 ` <4FA7DBE6.3060809-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-07 14:48                   ` Alan Stern
     [not found]                     ` <Pine.LNX.4.44L0.1205071046350.1602-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-05-08  7:53                       ` Igor Grinberg
     [not found]                         ` <4FA8D108.7090004-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2012-05-08 16:24                           ` Greg Kroah-Hartman
2012-05-09  6:25                             ` Igor Grinberg
2012-05-09  7:31                             ` Igor Grinberg

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=20120507080907.GB3229@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=Keshava_mgowda@ti.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=grinberg@compulab.co.il \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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