linux-kernel - Re: next phase of tmem into linux-next

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: <20110601142544.62494a52.sfr@canb.auug.org.au>
Date:	Wed, 1 Jun 2011 14:25:44 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Dan Magenheimer <dan.magenheimer@...cle.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Konrad Wilk <konrad.wilk@...cle.com>
Subject: Re: next phase of tmem into linux-next

Hi Dan,

On Tue, 31 May 2011 17:49:21 -0700 (PDT) Dan Magenheimer <dan.magenheimer@...cle.com> wrote:
>
> Please re-include the following tree into linux-next.  The
> commit series is for frontswap, the complement of cleancache
> handling swap pages, which is the next phase in tmem.  It also
> includes the shim code to Xen tmem for frontswap.  It applies
> cleanly on linux-3.0-rc1, but if there are any problems or
> you have any questions, please let me know!
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/djm/tmem.git#linux-next

I don't remove trees from linux-next unless excplictly asked to, so this
tree is still included.  As long as you stick to the rules (posted,
reviewed, ready for Linus), anything you add to that tree will be
included.

The tree is still called "cleancache" in linux-next.  Should I change
that to something more generic?
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped