Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753454AbbD2FzJ (ORCPT ); Wed, 29 Apr 2015 01:55:09 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:33743 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751264AbbD2FzG (ORCPT ); Wed, 29 Apr 2015 01:55:06 -0400 Date: Wed, 29 Apr 2015 00:53:34 -0500 From: Felipe Balbi To: "Du, Changbin" CC: "balbi@ti.com" , "stable@vger.kernel.org" , "gregkh@linuxfoundation.org" , "linux-usb@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Cohen, David A" , "Wu, Hao" Subject: Re: [PATCH] usb: gadget: composite: enable BESL support Message-ID: <20150429055334.GA29821@saruman.tx.rr.com> Reply-To: References: <0C18FE92A7765D4EB9EE5D38D86A563A01CDD6AE@SHSMSX103.ccr.corp.intel.com> <20150428154501.GA18263@saruman.tx.rr.com> <0C18FE92A7765D4EB9EE5D38D86A563A01CDED1E@SHSMSX103.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <0C18FE92A7765D4EB9EE5D38D86A563A01CDED1E@SHSMSX103.ccr.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3768 Lines: 107 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 29, 2015 at 03:04:51AM +0000, Du, Changbin wrote: > > > From: Felipe Balbi > > > Date: Tue, 30 Sep 2014 16:08:03 -0500 > > > Subject: [PATCH] usb: gadget: composite: enable BESL support > >=20 > > missing upstream commit. > >=20 > > > According to USB 2.0 ECN Errata for Link Power Management > > > (USB2-LPM-Errata-final.pdf), BESL must be enabled if LPM is enabled. > > > > > > This helps with USB30CV TD 9.21 LPM L1 Suspend Resume Test. > > > > > > Cc: # 3.14 > >=20 > > this should be backported all the way back to 3.1. The commit which this > > patch is fixing, was applied on v3.1, so we're probably going to backpo= rt to > > 3.10 and 3.14. When asking for backports, don't consider only your proj= ect, > > think about the kernel/stable releases as a whole. > >=20 > > BTW, that should be v3.1+, the + tells the Stable team that from v3.1 f= orward, > > all kernels need the backport. > >=20 > > > Signed-off-by: Felipe Balbi > > > Signed-off-by: Du, Changbin > > > --- > > > Hi, > > > > > > This patch was introduced on v3.18. However the issue fixed already > > > existed on > > > v3.14 and v3.14 is a long term support version. > >=20 > > the issue already existed on v3.1, why did you decide to backport only = to > > v3.14 ? > >=20 > > > So propose to backport it over there as well. > > > > > -- > > balbi >=20 > Thanks for pointing it out, Balbi. Sorry for not considering the whole > trees. This is my first time to send backport request and now know how > do it well. I will resend request with field updated. ok, things which usually help are: 'git log -SLPM -- drivers/usb/gadget/composite.c' this will help you find commits which have the string LPM in their body and touch drivers/usb/gadget/composite.c 'git describe' this will tell you when a commit was merged. Keep in mind that a commit reaches a maintainer tree before Linus tags something, so if git describe says: v3.0-rc3-212-gfoobar, that means commit reaches mainline during v3.1 merge window. Documentation/stable_kernel_rules.txt This tells what a stable patch should look like 'git remote add stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git \ && git fetch stable && git log stable/linux-3.14.y' This would help you see actual commits in a stable tree so you can mimic the format. cheers --=20 balbi --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVQHHeAAoJEIaOsuA1yqREMBoP/1O3xnCcoTYDGnNMqCpLY+C8 IJv+IlS1y/tdyiAyU0EoRYT8zBXl+Rq35IR0bcaclR0QoMFytTqFN3JvONWwH2hD 4aab58I0ZB7WhCwIox3XW+Q5KHFi+vtizbjI+3GG48hpUhUB+JklNr3sDrK9P+d/ 2lakTI3ojtCtM5+pjLHyX3h6GofWtO9dJ63y7TW0OZtYZjN4n5iAaYVSmCmQOG3F a9mHo30FPS/kEckf8aXHvDN23TamoNuGkqznt0nGF5ATowhCYS2ipkcTEN7dEVnb 1W4KUzewMRJNJZn9W4QaB9zwLEUI8wrrrrwbT3NuNhuSPPkDSKEi44829wHGh7SZ DVwTvNYDyrnWNUT60jx5MMwM7vH12AaOEt1q8ADSS5QPsXERPavDLO4wEJu5BHQn z+S+Rg6X7Z8ZX0zyrJ2DzHvzQzFu9AJhTYDzsdKnUAV8DA+zmObAyC+thuB9XLQd s1MadkCSMe6fKSLxoP0ijm2deGHWgRiwKFNxX/YMkfVXKN5PTsoaiUKUb4gqulx4 /Kw/vc7JZWPxZ7zV0CRdM/70tsoHiDYKGEZRtkPtSNcY62XWyC6GzAJSgQ9uKUQm 1MEKUUbL64G8bwmmqSQXvDUhrm7MymiWYDxSPmjnEV4wKH4scUPGtZr3GrfLK2Zf lLZrYOtwgVSXwttFLiQ7 =hCS1 -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/