On Wed, Apr 30, 2014 at 03:08:49PM +0800, Rui Xiang wrote: > v2: > As Ben suggested, adjust the patches order and add a supplement from > 3.2.x for commit ebebd49a8eab. > > ----- > > Hi Greg, > > These are the part IV commits that I've analized from the list of > upstream commits that have been backported to 3.2 but missing from 3.4. > > For the 16 commits, > - 12 commits were marked for stable but can't be applied cleanly to > 3.4.x. > - 3 commits have no stable tag. I've found out why they were backported > to 3.2.x, and I'm sure they should be applied to 3.4.x. > - 1 commit was only intrduced in 3.2 by Ben, as a supplement for commit > ebebd49a8eab '8250/16?50: Add support for Broadcom TruManage redirected > serial port', and it was suitable for 3.4.x, too. [*] > > Please cherry-pick these commits from 3.2.x: > 6af864ccfe6d [SCSI] isci: Fix a race condition in the SSP task management path > e4498ad1ef9c [SCSI] mpt2sas: Fix for device scan following host reset could get stuck in a infinite loop > 93cfcb8c998e [SCSI] mpt2sas: Fix for issue Missing delay not getting set during system bootup > fa1dd81ceffe [SCSI] hpsa: gen8plus Smart Array IDs > 9ef928b0104a iscsi-target: Always send a response before terminating iSCSI connection > 5874fd1d23ed target/pscsi: fix return value check > d801775a8e97 target: Fix MAINTENANCE_IN service action CDB checks to use lower 5 bits > b60dc9751a36 target: use correct sense code for LUN communication failure > 1506cb20191c target/file: Fix 32-bit highmem breakage for SGL -> iovec mapping > 4f31ab80a2bf serial: pch_uart: fix tty-kref leak in dma-rx path > 73449fe73fa3 serial: pch_uart: fix tty-kref leak in rx-error path > 689901ce9ced tty: Correct tty buffer flush. > > There are 4 other commits that need some adjustments. The following are the backports. All now applied, thanks. I think I've caught up on all pending 3.4 patches that have been sent in. If not, please resend. thanks, 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