On Mon, Mar 17, 2014 at 10:12:11AM +0800, Yang Yingliang wrote: > Hi Greg, > > We've started to analize the list of upstream commits that have been > backported to 3.2 but missing from 3.4. Here is part 5. > > For the 13 commits that I've analized, > - 10 commits were marked for stable but can't be applied cleanly to 3.4. > - 2 commits have no stable tag. I've found out why they were backported to 3.2.x, > and I'm sure they shoud be applied to 3.4.x.(*) > - 1 commit was marked for stable but I found out it has been dropped from the > stable tree.(**) > > Please first cherry-pick that commit from mainline: > > b62cd96de316 usb: dwc3: pci: add support for BayTrail (*) > > then, cherry-pick those commits from 3.2.x: > > 798761949ee8 usb: dwc3: add support for Merrifield > 7e6337b69496 usb: Disable USB 2.0 Link PM before device reset. > d83ceadbcef3 usb: wusbcore: set the RPIPE wMaxPacketSize value correctly > 4a6c6bb2be9c usb: wusbcore: change WA_SEGS_MAX to a legal value > 75a4cfafc737 USB: ftdi_sio: fixed handling of unsupported CSIZE setting > fea5417579fa ahci: Add Device IDs for Intel Wellsburg PCH (*) > d23288a5a9fb ahci: AHCI-mode SATA patch for Intel Coleto Creek DeviceIDs > dc77997de6b3 xhci: Don't enable/disable RWE on bus suspend/resume. > 17318fb39430 ahci: Add Device IDs for Intel Wildcat Point-LP > > There're 2 other commits that need trivial context adjustments. I'll send out > the backports. > > (**) The commit is 2435dcb98cfe (ahci: add support for IBM Akebono platform device) > There's no support for the Akebono board in even 3.13-rcX, so this commit is useless > for 3.4.x. All now applied, many thanks for this work. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html