[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160601012632.GE461@swordfish>
Date: Wed, 1 Jun 2016 10:26:32 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: sergey.senozhatsky@...il.com, Joonsoo Kim <iamjoonsoo.kim@....com>,
Minchan Kim <minchan@...nel.org>, mm-commits@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: + zram-switch-to-crypto-compress-api.patch added to -mm tree
On (05/31/16 12:10), akpm@...ux-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
Powered by blists - more mailing lists