public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Piotr Sarna <p.sarna@partner.samsung.com>
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
Date: Wed, 31 Jul 2013 12:16:36 +0200	[thread overview]
Message-ID: <51F8E404.6070507@partner.samsung.com> (raw)
In-Reply-To: <20130730135333.GB27962@kroah.com>

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

  reply	other threads:[~2013-07-31 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 12:30 [PATCH 1/2] staging: zram: add Crypto API support Piotr Sarna
2013-07-30 12:30 ` [PATCH 2/2] staging: zram: add per-cpu support to Crypto Piotr Sarna
2013-07-30 18:45   ` Sergey Senozhatsky
2013-07-30 13:53 ` [PATCH 1/2] staging: zram: add Crypto API support Greg KH
2013-07-31 10:16   ` Piotr Sarna [this message]
2013-07-31 12:49     ` Greg KH
2013-07-31 13:31       ` Piotr Sarna
2013-07-31 13:47 ` Minchan Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51F8E404.6070507@partner.samsung.com \
    --to=p.sarna@partner.samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ngupta@vflare.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox