From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Wilk <konrad.wilk@oracle.com>
Subject: next phase of tmem into linux-next
Date: Tue, 31 May 2011 17:49:21 -0700 (PDT) [thread overview]
Message-ID: <80f7ab04-7ae6-48cb-b254-e99343147bf0@default> (raw)
Hi Stephen --
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
Thanks,
Dan
next reply other threads:[~2011-06-01 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 0:49 Dan Magenheimer [this message]
2011-06-01 4:25 ` next phase of tmem into linux-next Stephen Rothwell
2011-06-01 16:22 ` Dan Magenheimer
2011-06-01 23:48 ` Stephen Rothwell
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=80f7ab04-7ae6-48cb-b254-e99343147bf0@default \
--to=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).