From: Luis Chamberlain <mcgrof@kernel.org>
To: tangmeng <tangmeng@uniontech.com>
Cc: Matthew Wilcox <willy@infradead.org>,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
keescook@chromium.org, yzaikin@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
nizhen@uniontech.com, zhanglianjie@uniontech.com,
nixiaoming@huawei.com, sujiaxun@uniontech.com
Subject: Re: [PATCH 10/11] fs/drop_caches: move drop_caches sysctls to its own file
Date: Sat, 26 Feb 2022 13:00:53 -0800 [thread overview]
Message-ID: <YhqVBcHRdctU65S/@bombadil.infradead.org> (raw)
In-Reply-To: <8940d534-d6e5-0642-f145-67a323eb8092@uniontech.com>
On Wed, Feb 23, 2022 at 05:51:33PM +0800, tangmeng wrote:
> On 2022/2/23 08:39, Luis Chamberlain wrote:
> >
> > Since you are following up on more changes, can you work on this?
> > Brownie points if you show size results to refelct no size difference
> > based on a new build with an example new user.
> >
>
> I'm going work on this, but I think it may take some times to get it done.
Thanks and good stuff! Can you please then make that the focus of your
first set of patches, and then respin this series by collecting all
ACKs, Reviwed-bys? Yes please send a new v3 series for it. While at it
please Cc the other folks doing sysctls changes so they are aware of
this.
Thanks!
Luis
prev parent reply other threads:[~2022-02-26 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 6:06 tangmeng
2022-02-20 11:40 ` Matthew Wilcox
2022-02-21 1:55 ` tangmeng
2022-02-23 0:39 ` Luis Chamberlain
2022-02-23 9:51 ` tangmeng
2022-02-26 21:00 ` Luis Chamberlain [this message]
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=YhqVBcHRdctU65S/@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nixiaoming@huawei.com \
--cc=nizhen@uniontech.com \
--cc=sujiaxun@uniontech.com \
--cc=tangmeng@uniontech.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yzaikin@google.com \
--cc=zhanglianjie@uniontech.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