On Thu, Nov 26, 2015 at 12:04:49AM +0900, Sergey Senozhatsky wrote: > Hello, > > On (11/25/15 22:50), Minchan Kim wrote: > [..] > > > I think that applying 3/3 before 2/3 will be a simpler (and probably a > > > better) > > > thing to do. We fitst extend zcomp interface and pass flags (without any > > > functional change) and then extend the flags and introduce vmalloc > > > fallback. > > > > The reason I ordered such way is that I wanted to discuss [2/3] as > > stable material after I get your ACK. It solves real problem in android > > platform > > which is real fact and I think it's enough small to send stable tree. > > What do you think? > > > > > > > > So we don't have to add comments to lz4/lzo backend that are getting > > > (re-)moved > > > in the very next commit. > > > > Fair enough if you don't agree sending [2/3] to stable. > > Aha, I see. I don't mind to send it to -stable (with __GFP_HIGHMEM fix > up).
Sure. Can I add your acked-by for [2/3] and [3/3]? And I will keep order and add stable mark in [2/3]. > > Do -stable guys take this type of patches? I think so because it's real problem fix and enough small to backport. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
