linux-kernel - Re: [PATCH 1/2] staging: zram: add Crypto API support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130730135333.GB27962@kroah.com>
Date:	Tue, 30 Jul 2013 06:53:33 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Piotr Sarna <p.sarna@...tner.samsung.com>
Cc:	ngupta@...are.org, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org, b.zolnierkie@...sung.com,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCH 1/2] staging: zram: add Crypto API support

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.

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?...

thanks,

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