[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c5f278da-ec68-3206-d91b-d1ca7c97bb8c@wangsu.com>
Date: Thu, 19 Sep 2019 09:32:48 +0800
From: Lin Feng <linf@...gsu.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: corbet@....net, mcgrof@...nel.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
keescook@...omium.org, mchehab+samsung@...nel.org,
mgorman@...hsingularity.net, vbabka@...e.cz, ktkhai@...tuozzo.com,
hannes@...xchg.org, willy@...radead.org,
kbuild test robot <lkp@...el.com>
Subject: Re: [PATCH] [RESEND] vmscan.c: add a sysctl entry for controlling
memory reclaim IO congestion_wait length
On 9/18/19 20:27, Michal Hocko wrote:
> Please do not post a new version with a minor compile fixes until there
> is a general agreement on the approach. Willy had comments which really
> need to be resolved first.
Sorry, but thanks for pointing out.
>
> Also does this
> [...]
>> Reported-by: kbuild test robot<lkp@...el.com>
> really hold? Because it suggests that the problem has been spotted by
> the kbuild bot which is kinda unexpected... I suspect you have just
> added that for the minor compilation issue that you have fixed since the
> last version.
Yes, I do know the issue is not reported by the robot, but
just followed the kbuild robot tip, this Reported-by suggested by kbuild robot
seems a little misleading, I'm not sure if it has other meanings.
'If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@...el.com>'
Powered by blists - more mailing lists