From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752620AbbKYPGX (ORCPT ); Wed, 25 Nov 2015 10:06:23 -0500 Received: from mail-pa0-f42.google.com ([209.85.220.42]:33700 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751060AbbKYPGV (ORCPT ); Wed, 25 Nov 2015 10:06:21 -0500 Date: Thu, 26 Nov 2015 00:04:49 +0900 From: Sergey Senozhatsky To: Minchan Kim Cc: Sergey Senozhatsky , Andrew Morton , linux-kernel@vger.kernel.org, Kyeongdon Kim Subject: Re: [PATCH v2 3/3] zram: pass gfp from zcomp frontend to backend Message-ID: <20151125150449.GA579@swordfish> References: <1448430673-10766-1-git-send-email-minchan@kernel.org> <1448430673-10766-3-git-send-email-minchan@kernel.org> <20151125124647.GA525@swordfish> <20151125135020.GA12747@bbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151125135020.GA12747@bbox> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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). Do -stable guys take this type of patches? -ss