On Fri, Mar 13 2015 at 8:37am -0400, Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> wrote: > On (03/13/15 08:24), Mike Snitzer wrote: > > Thanks, but I already fixed these 2 patches and pushed them to > > linux-dm.git's for-next branch last night (I also posted v3 of the > > corresponding patches to LKML at that time). > > oh, I see. didn't know that. > > > Sorry to waste your time, I've learned my lesson: > > > > no problem. > > > Hopefully linux-next was able to pick up my new 'for-next' and we don't > > have an entire weekend of linux-next crashes due to my idiocy. > > nope, this is how I spot it -- next-20150313 doesn't boot. Hi Stephen, Is there any opportunity to get the tree fixed by re-pulling linux-dm.git's 'for-next'? I'd hate to kill linux-next productivity this weekend! Sorry about this. Please advise, thanks. Mike -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
