Message-id: <51F8E404.6070507@partner.samsung.com>
Date: Wed, 31 Jul 2013 12:16:36 +0200
From: Piotr Sarna <p.sarna@partner.samsung.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623
 Thunderbird/17.0.7
MIME-version: 1.0
To: Greg KH <gregkh@linuxfoundation.org>
Cc: ngupta@vflare.org, linux-kernel@vger.kernel.org,
        devel@driverdev.osuosl.org, b.zolnierkie@samsung.com,
        Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH 1/2] staging: zram: add Crypto API support
References: <1375187449-6546-1-git-send-email-p.sarna@partner.samsung.com>
 <20130730135333.GB27962@kroah.com>
In-reply-to: <20130730135333.GB27962@kroah.com>
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1393
Lines: 35

Hi,

On 07/30/2013 03:53 PM, Greg KH wrote:
> On Tue, Jul 30, 2013 at 02:30:48PM +0200, Piotr Sarna wrote:
>> Current version of zram does not allow any substitution of a default
>> compression algorithm. Therefore, I decided to change the existing
>> implementation of page compression by adding Crypto API compability.
> 
> As I have stated before, I want this code to get merged out of the
> drivers/staging/ area _before_ any new features get added to it.  People
> are taking too much time adding new stuff, like this, and no one seems
> to be working to get it merged to the proper place anymore.
> 

OK, but we actually need those features in order to test zram
against other, competitive solutions - and then decide whether
and how to merge it out of /drivers/staging.

> So again, I'm going to have to say no to a new feature here, sorry.
> zcache, zram, and zsmalloc need to get cleaned up and merged out of
> staging before anything new can be added to them.
> 
> Or, if no one is working on that, I guess I can just delete them,
> right?...
> 

Is there any official TODO list of cleaning up and merging out zram?

Regards,
Piotr Sarna
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/