On Mon, May 11, 2015 at 05:21:51AM -0700, Greg KH wrote: > On Mon, May 11, 2015 at 05:39:44PM +0800, Shannon Zhao wrote: > > Ping? > > Large series of backports usually take me a while to get to as they are > outside of my "normal" workflow. Usually they take a few months to get > into the tree, waiting for a "slack time". I still have a number of > other series that have yet to be merged that were sent a long time > before yours. Please be patient. Actually, why aren't these being marked for -stable in the first place? Going back and adding them "by hand" like this is a big pain, especially when I have to hand-verify each git commit id, as the first one I looked at is incorrect and now I don't trust any of them in the series. Please work with the "normal" stable kernel workflow and mark the patches properly so that you don't have to do this extra work, and I don't either. Right now I'm going to just dump this whole series from my queue. Please just give me a series of git commit ids that should be applied to the 3.14-stable kernel tree, and in what order they should be applied in. If any need to be backported differently, please send those as a separate series, and I will get to them at a different time, as that is a lot more work having to hand-verify everything. 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