linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-mm@kvack.org,
	ngupta@vflare.org, konrad.wilk@oracle.com,
	sjenning@linux.vnet.ibm.com, minchan@kernel.org,
	dan.magenheimer@oracle.com
Subject: [PATCH V2 0/5] staging: zcache: move new zcache code base from ramster
Date: Fri, 18 Jan 2013 13:24:22 -0800	[thread overview]
Message-ID: <1358544267-9104-1-git-send-email-dan.magenheimer@oracle.com> (raw)

[V2: no code changes, patchset now generated via git format-patch -M]

Hi Greg --

With "old zcache" now removed, we can now move "new zcache" from its
temporary home (in drivers/staging/ramster) to reclaim sole possession
of the name "zcache".

(Note that [PATCH 2/5] is just a git mv.)

This patchset should apply cleanly to staging-next.

Thanks,
Dan

Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>

---
Diffstat:

 drivers/staging/Kconfig                            |    4 +-
 drivers/staging/Makefile                           |    2 +-
 drivers/staging/ramster/Kconfig                    |   31 -
 drivers/staging/ramster/Makefile                   |    6 -
 drivers/staging/ramster/ramster.h                  |   59 -
 drivers/staging/ramster/ramster/heartbeat.c        |  462 ----
 drivers/staging/ramster/ramster/heartbeat.h        |   87 -
 drivers/staging/ramster/ramster/masklog.c          |  155 --
 drivers/staging/ramster/ramster/masklog.h          |  220 --
 drivers/staging/ramster/ramster/nodemanager.c      |  995 ---------
 drivers/staging/ramster/ramster/nodemanager.h      |   88 -
 drivers/staging/ramster/ramster/r2net.c            |  414 ----
 drivers/staging/ramster/ramster/ramster.c          |  985 ---------
 drivers/staging/ramster/ramster/ramster.h          |  161 --
 .../staging/ramster/ramster/ramster_nodemanager.h  |   39 -
 drivers/staging/ramster/ramster/tcp.c              | 2253 --------------------
 drivers/staging/ramster/ramster/tcp.h              |  159 --
 drivers/staging/ramster/ramster/tcp_internal.h     |  248 ---
 drivers/staging/ramster/tmem.c                     |  894 --------
 drivers/staging/ramster/tmem.h                     |  259 ---
 drivers/staging/ramster/zbud.c                     | 1060 ---------
 drivers/staging/ramster/zbud.h                     |   33 -
 drivers/staging/ramster/zcache-main.c              | 1820 ----------------
 drivers/staging/ramster/zcache.h                   |   53 -
 drivers/staging/zcache/Kconfig                     |   26 +
 drivers/staging/zcache/Makefile                    |    6 +
 drivers/staging/zcache/ramster.h                   |   59 +
 drivers/staging/zcache/ramster/heartbeat.c         |  462 ++++
 drivers/staging/zcache/ramster/heartbeat.h         |   87 +
 drivers/staging/zcache/ramster/masklog.c           |  155 ++
 drivers/staging/zcache/ramster/masklog.h           |  220 ++
 drivers/staging/zcache/ramster/nodemanager.c       |  995 +++++++++
 drivers/staging/zcache/ramster/nodemanager.h       |   88 +
 drivers/staging/zcache/ramster/r2net.c             |  414 ++++
 drivers/staging/zcache/ramster/ramster.c           |  985 +++++++++
 drivers/staging/zcache/ramster/ramster.h           |  161 ++
 .../staging/zcache/ramster/ramster_nodemanager.h   |   39 +
 drivers/staging/zcache/ramster/tcp.c               | 2253 ++++++++++++++++++++
 drivers/staging/zcache/ramster/tcp.h               |  159 ++
 drivers/staging/zcache/ramster/tcp_internal.h      |  248 +++
 drivers/staging/zcache/tmem.c                      |  894 ++++++++
 drivers/staging/zcache/tmem.h                      |  259 +++
 drivers/staging/zcache/zbud.c                      | 1060 +++++++++
 drivers/staging/zcache/zbud.h                      |   33 +
 drivers/staging/zcache/zcache-main.c               | 1820 ++++++++++++++++
 drivers/staging/zcache/zcache.h                    |   53 +
 46 files changed, 10479 insertions(+), 10484 deletions(-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2013-01-18 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 21:24 Dan Magenheimer [this message]
2013-01-18 21:24 ` [PATCH 1/5] staging: ramster: disable build in anticipation of renaming Dan Magenheimer
2013-01-18 21:24 ` [PATCH 2/5] staging: zcache: rename ramster to zcache Dan Magenheimer
2013-01-19 19:57   ` Dan Carpenter
2013-01-22 17:04     ` Dan Magenheimer
2013-01-18 21:24 ` [PATCH 3/5] staging: zcache: adjustments to config/build files due to renaming Dan Magenheimer
2013-01-18 21:24 ` [PATCH 4/5] staging: zcache: re-enable config/build of zcache after renaming Dan Magenheimer
2013-01-18 21:24 ` [PATCH 5/5] staging: zcache: fix uninitialized variable compile warning Dan Magenheimer
2013-01-18 21:46 ` [PATCH V2 0/5] staging: zcache: move new zcache code base from ramster Greg KH
2013-01-18 21:56 ` Konrad Rzeszutek Wilk

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=1358544267-9104-1-git-send-email-dan.magenheimer@oracle.com \
    --to=dan.magenheimer@oracle.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=sjenning@linux.vnet.ibm.com \
    /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).