From: Felipe Balbi <balbi@ti.com>
To: Paolo Pisati <paolo.pisati@canonical.com>
Cc: Felipe Balbi <balbi@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>, Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
<linux-kernel@vger.kernel.org>,
Robert Nelson <robertcnelson@gmail.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] regulator: core: if voltage scaling fails, restore original voltage values
Date: Fri, 14 Dec 2012 17:40:30 +0200 [thread overview]
Message-ID: <20121214154030.GD18233@arwen.pp.htv.fi> (raw)
In-Reply-To: <20121214153943.GA3306@luxor.wired.org>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Hi,
On Fri, Dec 14, 2012 at 04:39:43PM +0100, Paolo Pisati wrote:
> On Thu, Dec 13, 2012 at 11:47:15AM +0200, Felipe Balbi wrote:
> > On Thu, Dec 13, 2012 at 10:13:00AM +0100, Paolo Pisati wrote:
> > > Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
> > > Tested-by: Robert Nelson <robertcnelson@gmail.com>
> >
> > please read Documentation/stable_kernel_rules.txt, you'll see this is
> > wrong.
>
> you mean that i should have waited for the commit to hit Linus's tree before
> cc-ing stable?
No no, I mean that before you SoB you should have a:
Cc: <stable@vger.kernel.org> # v3.x v3.y ...
Something like the commit below:
commit 041d81f493d90c940ec41f0ec98bc7c4f2fba431
Author: Felipe Balbi <balbi@ti.com>
Date: Thu Oct 4 11:58:00 2012 +0300
usb: dwc3: gadget: fix 'endpoint always busy' bug
If a USB transfer has already been started, meaning
we have already issued StartTransfer command to that
particular endpoint, DWC3_EP_BUSY flag has also
already been set.
When we try to cancel this transfer which is already
in controller's cache, we will not receive XferComplete
event and we must clear DWC3_EP_BUSY in order to allow
subsequent requests to be properly started.
The best place to clear that flag is right after issuing
DWC3_DEPCMD_ENDTRANSFER.
Cc: stable@vger.kernel.org # v3.4 v3.5 v3.6
Reported-by: Moiz Sonasath <m-sonasath@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-14 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 9:12 [PATCH] [resend] regulator: core: if voltage scaling fails, restore original values Paolo Pisati
2012-12-13 9:13 ` [PATCH] regulator: core: if voltage scaling fails, restore original voltage values Paolo Pisati
2012-12-13 9:47 ` Felipe Balbi
2012-12-14 15:39 ` Paolo Pisati
2012-12-14 15:40 ` Felipe Balbi [this message]
2012-12-15 14:15 ` Mark Brown
2012-12-15 14:57 ` Felipe Balbi
2012-12-17 14:15 ` Mark Brown
2012-12-17 15:18 ` Felipe Balbi
2012-12-17 15:45 ` Mark Brown
2012-12-17 23:23 ` [PATCH] [stable-resend] " Paolo Pisati
2012-12-27 17:03 ` Ben Hutchings
2012-12-15 14:53 ` [PATCH] " Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2012-12-12 11:45 [PATCH] regulator: core: if voltage scaling fails, restore original Paolo Pisati
2012-12-12 11:45 ` [PATCH] regulator: core: if voltage scaling fails, restore original voltage values Paolo Pisati
2012-12-12 18:13 ` Robert Nelson
2012-12-12 19:00 ` Felipe Balbi
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=20121214154030.GD18233@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=paolo.pisati@canonical.com \
--cc=paul@pwsan.com \
--cc=robertcnelson@gmail.com \
--cc=stable@vger.kernel.org \
/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