From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757067AbcFAB0h (ORCPT ); Tue, 31 May 2016 21:26:37 -0400 Received: from mail-pf0-f195.google.com ([209.85.192.195]:36108 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757014AbcFAB0g (ORCPT ); Tue, 31 May 2016 21:26:36 -0400 Date: Wed, 1 Jun 2016 10:26:32 +0900 From: Sergey Senozhatsky To: Andrew Morton Cc: sergey.senozhatsky@gmail.com, Joonsoo Kim , Minchan Kim , mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: + zram-switch-to-crypto-compress-api.patch added to -mm tree Message-ID: <20160601012632.GE461@swordfish> References: <574de1b2.LDeSluXYR1Ke9MvG%akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <574de1b2.LDeSluXYR1Ke9MvG%akpm@linux-foundation.org> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (05/31/16 12:10), akpm@linux-foundation.org wrote: > The patch titled > Subject: zram: switch to crypto compress API > has been added to the -mm tree. Its filename is > zram-switch-to-crypto-compress-api.patch > > This patch should soon appear at > http://ozlabs.org/~akpm/mmots/broken-out/zram-switch-to-crypto-compress-api.patch > and later at > http://ozlabs.org/~akpm/mmotm/broken-out/zram-switch-to-crypto-compress-api.patch Andrew, I'd prefer this patch to also include changes from this one: http://ozlabs.org/~akpm/mmots/broken-out/zram-align-zcomp-interface-to-crypto-comp-api.patch (http://article.gmane.org/gmane.linux.kernel/2231316) (per Minchan). IOW, squash http://ozlabs.org/~akpm/mmots/broken-out/zram-switch-to-crypto-compress-api.patch and http://ozlabs.org/~akpm/mmots/broken-out/zram-align-zcomp-interface-to-crypto-comp-api.patch what's the best way to do it? should I resend the series? -ss