From: Chao Yu <yuchao0@huawei.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-erofs@lists.ozlabs.org>,
<devel@driverdev.osuosl.org>, <linux-fsdevel@vger.kernel.org>,
<linux-btrfs@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>, <linux-mm@kvack.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Gao Xiang <gaoxiang25@huawei.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jaegeuk Kim <jaegeuk@kernel.org>, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
<ocfs2-devel@oss.oracle.com>
Subject: Re: [PATCH 2/3] mm: remove cleancache.c
Date: Tue, 28 May 2019 09:24:45 +0800 [thread overview]
Message-ID: <8f69d56d-3fdd-a160-9574-f81bd066e5ac@huawei.com> (raw)
In-Reply-To: <20190527103207.13287-3-jgross@suse.com>
On 2019/5/27 18:32, Juergen Gross wrote:
> With the removal of tmem and xen-selfballoon the only user of
> cleancache is gone. Remove it, too.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> Documentation/vm/cleancache.rst | 296 ------------------------------------
> Documentation/vm/frontswap.rst | 10 +-
> Documentation/vm/index.rst | 1 -
> MAINTAINERS | 7 -
> drivers/staging/erofs/data.c | 6 -
> drivers/staging/erofs/internal.h | 1 -
> fs/block_dev.c | 5 -
> fs/btrfs/extent_io.c | 9 --
> fs/btrfs/super.c | 2 -
> fs/ext4/readpage.c | 6 -
> fs/ext4/super.c | 2 -
> fs/f2fs/data.c | 3 +-
For erofs and f2fs part,
Acked-by: Chao Yu <yuchao0@huawei.com>
Thanks,
> fs/mpage.c | 7 -
> fs/ocfs2/super.c | 2 -
> fs/super.c | 3 -
> include/linux/cleancache.h | 124 ---------------
> include/linux/fs.h | 5 -
> mm/Kconfig | 22 ---
> mm/Makefile | 1 -
> mm/cleancache.c | 317 ---------------------------------------
> mm/filemap.c | 11 --
> mm/truncate.c | 15 +-
next prev parent reply other threads:[~2019-05-28 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 10:32 [PATCH 0/3] remove tmem and code depending on it Juergen Gross
2019-05-27 10:32 ` [PATCH 1/3] xen: remove tmem driver Juergen Gross
2019-05-28 22:44 ` Boris Ostrovsky
2019-05-27 10:32 ` [PATCH 2/3] mm: remove cleancache.c Juergen Gross
2019-05-27 13:10 ` David Sterba
2019-05-28 0:50 ` Joseph Qi
2019-05-28 1:24 ` Chao Yu [this message]
2019-05-27 10:32 ` [PATCH 3/3] mm: remove tmem specifics from frontswap Juergen Gross
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=8f69d56d-3fdd-a160-9574-f81bd066e5ac@huawei.com \
--to=yuchao0@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=devel@driverdev.osuosl.org \
--cc=dsterba@suse.com \
--cc=gaoxiang25@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=jgross@suse.com \
--cc=jlbec@evilplan.org \
--cc=josef@toxicpanda.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).