linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Oussama Ghorbel <ghorbel@pivasoftware.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Rabin Vincent <rabin@rab.in>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] phy: omap-usb2: Enable runtime PM of omap-usb2 phy properly
Date: Wed, 8 Oct 2014 14:42:56 +0300	[thread overview]
Message-ID: <54352340.3050900@ti.com> (raw)
In-Reply-To: <543517F9.9070109@pivasoftware.com>

Oussama,

On 10/08/2014 01:54 PM, Oussama Ghorbel wrote:
> Hi Roger,
> 
> Should I resend this v2 version of the patch to stable@vger.kernel.org which is suitable for v3.17 and which will require a very tiny adaptation?
> Or I should resend the first version of this patch which is suitable for 3.16 but might seems confusing a little sine I'm resend the outdated version.

If it is a trivial conflict then I think you can just send the patch which applies to the most recent kernel.
Greg can clarify if I'm wrong as he maintains the stable trees.

cheers,
-roger

> 
> Thanks,
> Oussama
> On 10/08/2014 09:17 AM, Roger Quadros wrote:
>> Hi Oussama,
>>
>> On 10/07/2014 02:02 PM, Oussama Ghorbel wrote:
>>> The USB OTG port does not work since v3.16 on omap platform.
>>> This is a regression introduced by the commit
>>> eb82a3d846fa (phy: omap-usb2: Balance pm_runtime_enable() on probe failure
>>>   and remove).
>>> This because the call to pm_runtime_enable() function is moved after the
>>> call to devm_phy_create() function, which has side effect since later in
>>> the subsequent calls of devm_phy_create() there is a check with
>>> pm_runtime_enabled() to configure few things.
>>>
>>> Signed-off-by: Oussama Ghorbel <ghorbel@pivasoftware.com>
>> Acked-by: Roger Quadros <rogerq@ti.com>
>>
>> Could you please send the patch to
>> Cc: <stable@vger.kernel.org>        [3.16+]
>>
>> That way it will get into 3.16 onwards. Thanks.
>>
>> cheers,
>> -roger
>>
> 


  reply	other threads:[~2014-10-08 11:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 16:15 [PATCH] phy: omap-usb2: Enable runtime PM of omap-usb2 phy properly Oussama Ghorbel
2014-09-26 13:17 ` Oussama Ghorbel
2014-10-06 19:44   ` Rabin Vincent
2014-10-07 11:02     ` [PATCHv2] " Oussama Ghorbel
2014-10-07 17:11       ` Rabin Vincent
2014-10-08  8:17       ` Roger Quadros
2014-10-08 10:54         ` Oussama Ghorbel
2014-10-08 11:42           ` Roger Quadros [this message]
2014-10-08 13:26             ` Greg KH
2014-10-08 13:50               ` Oussama Ghorbel
2014-10-29 23:09       ` Rabin Vincent
2014-10-30  5:16         ` Kishon Vijay Abraham I
2014-11-03 11:21       ` Kishon Vijay Abraham I
2014-11-03 23:29         ` Greg KH
2014-11-11 15:10           ` Enric Balletbo Serra

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=54352340.3050900@ti.com \
    --to=rogerq@ti.com \
    --cc=ghorbel@pivasoftware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rabin@rab.in \
    /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).