On Thu, Feb 23, 2012 at 08:41:08AM -0800, Greg KH wrote: > On Thu, Feb 23, 2012 at 02:24:13PM +0200, Felipe Balbi wrote: > > Hi Greg, > > > > Here are a few fixes for v3.3-rc5, they have been floating around for > > quite some time and nobody complained. A couple of them are quite > > obvious fixes. > > > > Please pull into your next batch of fixes for Linus. > > > > The following changes since commit b01543dfe67bb1d191998e90d20534dc354de059: > > > > Linux 3.3-rc4 (2012-02-18 15:53:33 -0800) > > > > are available in the git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git for-v3.3-rc5 > > > > for you to fetch changes up to 6f1a2f83bc8705ecff8ddc06ef249aecd18543a7: > > > > usb: fsl_udc_core: Fix scheduling while atomic dump message (2012-02-23 12:37:20 +0200) > > > > ---------------------------------------------------------------- > > Here are a few fixes for v3.3-rc5, nothing really > > major. The biggest thing is a remotely reproducible > > bug on DWC3 where wrapping around the list of TRBs > > isn't allowed with non-ISOC endpoints because we > > don't have a link TRB pointing to the beginning of > > the TRB pool. > > For -rc5 and later, I _really_ only want to take regression fixes, and, > at the most, new device ids if I happen to have some regression fixes > queued up. > > These all seem like legimate bug fixes, but nothing major that can't > wait for 3.4, right? Perhaps add them to 3.3-stable when they go to > Linus's tree during the 3.4-rc1 merge window instead of now? > > What do you think? that's fine. I will add them to proper branches and Cc stable, no problem at all. -- balbi
Attachment:
signature.asc
Description: Digital signature
