From: Luis Chamberlain <mcgrof@kernel.org>
To: tangmeng <tangmeng@uniontech.com>
Cc: 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
Subject: Re: [PATCH v2 10/11] fs/drop_caches: move drop_caches sysctls to its own file
Date: Wed, 6 Apr 2022 15:25:44 -0700 [thread overview]
Message-ID: <Yk4TaF0js35rRlVF@bombadil.infradead.org> (raw)
In-Reply-To: <d610e715-7806-18db-8551-0d0c2f71cbb6@uniontech.com>
On Wed, Mar 02, 2022 at 10:48:06AM +0800, tangmeng wrote:
>
>
> On 2022/2/27 05:02, Luis Chamberlain wrote:
>
> >
> > Thanks but please send a v3 including all the other patches as well
> > and collecting the Reviewed/Acked-bys, etc. This can be sent *after*
> > your v3 of the optimization work.
> >
> I have noticed that there is a conflict between sysctl-next and linux-next.
> Do I resubmit the patch based on linux-next, or after you deal with the
> conflict between sysctl-next and linux-next, I resubmit based on
> sysctl-next？
You can use sysctl-next now to base your development changes. Feel free
to send more changes.
Luis
prev parent reply other threads:[~2022-04-06 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 6:10 [PATCH v2 10/11] fs/drop_caches: move drop_caches sysctls to its own file tangmeng
2022-02-26 21:02 ` Luis Chamberlain
[not found] ` <d610e715-7806-18db-8551-0d0c2f71cbb6@uniontech.com>
2022-04-06 22:25 ` 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=Yk4TaF0js35rRlVF@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=tangmeng@uniontech.com \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).