[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Yk4TaF0js35rRlVF@bombadil.infradead.org>
Date: Wed, 6 Apr 2022 15:25:44 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: tangmeng <tangmeng@...ontech.com>
Cc: viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
keescook@...omium.org, yzaikin@...gle.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
nizhen@...ontech.com, zhanglianjie@...ontech.com,
nixiaoming@...wei.com
Subject: Re: [PATCH v2 10/11] fs/drop_caches: move drop_caches sysctls to its
own file
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
Powered by blists - more mailing lists