Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 6 Apr 2022 15:25:44 -0700
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
Message-ID: <Yk4TaF0js35rRlVF@bombadil.infradead.org>
References: <20220221061018.10472-1-tangmeng@uniontech.com>
 <YhqVW972rnF5L22U@bombadil.infradead.org>
 <d610e715-7806-18db-8551-0d0c2f71cbb6@uniontech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <d610e715-7806-18db-8551-0d0c2f71cbb6@uniontech.com>
Sender: Luis Chamberlain <mcgrof@infradead.org>
Precedence: bulk

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