From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, dan.magenheimer@oracle.com
Subject: [GIT PULL] (cleancache) stable/for-linus-3.4
Date: Mon, 19 Mar 2012 12:23:45 -0400 [thread overview]
Message-ID: <20120319162345.GA24647@phenom.dumpdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.git stable/for-linus-3.4
which has some patches for the cleancache API that should have been
submitted a _long_ time ago. They are basically cleanups:
- rename of flush to invalidate
- moving reporting of statistics into debugfs
- use __read_mostly as necessary.
Oh, and also the MAINTAINERS file change. The files (except the
MAINTAINERS file) have been in #linux-next for months now. The late
addition of MAINTAINERS file is a brain-fart on my side - didn't realize
I needed that just until I was typing this up - and I based that patch
on v3.3 - so the tree is on top of v3.3.
Please pull!
.../ABI/testing/sysfs-kernel-mm-cleancache | 11 --
Documentation/vm/cleancache.txt | 41 ++++----
MAINTAINERS | 7 ++
drivers/staging/zcache/zcache-main.c | 10 +-
drivers/xen/tmem.c | 10 +-
fs/block_dev.c | 2 +-
fs/super.c | 2 +-
include/linux/cleancache.h | 24 +++---
mm/cleancache.c | 98 ++++++++------------
mm/filemap.c | 2 +-
mm/truncate.c | 10 +-
11 files changed, 96 insertions(+), 121 deletions(-)
Dan Magenheimer (4):
mm: cleancache: s/flush/invalidate/
mm: zcache/tmem/cleancache: s/flush/invalidate/
mm: cleancache: report statistics via debugfs instead of sysfs.
mm: cleancache: Use __read_mostly as appropiate.
Konrad Rzeszutek Wilk (2):
MAINTAINERS: Adding cleancache API to the list.
Merge branch 'stable/cleancache.v13' into linux-next
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2012-03-19 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120319162345.GA24647@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.