On Wed, 24 Feb 2016 09:07:33 -0800 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Wed, Feb 24, 2016 at 09:21:14AM -0500, Steven Rostedt wrote: > > On Tue, 23 Feb 2016 19:37:04 -0800 > > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > On Tue, Feb 23, 2016 at 10:24:40PM -0500, Steven Rostedt wrote: > > > > On Tue, 23 Feb 2016 16:48:47 -0800 > > > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > > The patch below does not apply to the 3.14-stable tree. > > > > > If someone wants it applied there, or to any other stable or longterm > > > > > tree, then please email the backport, including the original git commit > > > > > id to <stable@xxxxxxxxxxxxxxx>. > > > > > > > > Hmm, strange. I just checked out v3.14.60 and did: > > > > > > > > $ git cherry-pick f37755490fe9bf76f6ba1d8c6591745d3574a6a6 > > > > > > > > and it applied without issue. > > > > > > Yes, it applies, sorry, but it breaks the build :( > > > > > > Same for 3.10-stable. It applies but can not compile. > > > > > > can you fix that up? > > > > Yep I'll go work on that. But can you change your scripts to say it > > broke the build, and possibly give a config file with it. The current > > email just says "The patch below does not apply to the 3.14-stable > > tree." > > The number of times that a patch applies but then breaks the build makes > it pretty low for me to write a new script for that, sorry... OK, then what about changing the wording to something like "The patch below does not apply or breaks the build for 3.14-stable tree" ? It would prevent people like me from bothering you about saying "but it does apply!" -- Steve -- 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