From: Sergey Senozhatsky Subject: Re: [PATCH v3 8/9] zram: use crypto API for compression Date: Fri, 25 Sep 2015 16:50:15 +0900 Message-ID: <20150925075015.GB865@swordfish> References: <1442553564-3476-1-git-send-email-iamjoonsoo.kim@lge.com> <1442553564-3476-9-git-send-email-iamjoonsoo.kim@lge.com> <20150921051903.GB863@swordfish> <20150925054326.GE7158@js1304-P5Q-DELUXE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Sergey Senozhatsky , Andrew Morton , Minchan Kim , Nitin Gupta , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Herbert Xu , "David S. Miller" , Stephan Mueller To: Joonsoo Kim Return-path: Received: from mail-pa0-f49.google.com ([209.85.220.49]:36142 "EHLO mail-pa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752305AbbIYHta (ORCPT ); Fri, 25 Sep 2015 03:49:30 -0400 Content-Disposition: inline In-Reply-To: <20150925054326.GE7158@js1304-P5Q-DELUXE> Sender: linux-crypto-owner@vger.kernel.org List-ID: On (09/25/15 14:43), Joonsoo Kim wrote: [..] > > > /* dynamic per-device compression frontend */ > > > struct zcomp { > > > void *stream; > > > - struct zcomp_backend *backend; > > > + const char *backend; > > > > ^^ what for? > > Will remove. I think that was my mistake, I realized why do you keep it later -- to allocate new zstreams. let's keep it. -ss