Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp654470ybe; Thu, 19 Sep 2019 01:26:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqyhMhDF+/dDXvFwU4dTtHWlV9taBNtp/QFoK3tjpVSUVGDp343VM67+wjgpfub44gTRHLbP X-Received: by 2002:a17:906:bb0f:: with SMTP id jz15mr12910800ejb.264.1568881572144; Thu, 19 Sep 2019 01:26:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568881572; cv=none; d=google.com; s=arc-20160816; b=KQottJ4HPDcfee1CQ22IJuzkULwvCLqBQUnlEhX6+v0oHsZ+2OKcILjiJ8B7dFjxRI QvGKDY1Pmnl34wIITsT0EQTjxJliwsVCoUjPoKsEme4yTGkQTQfrSdzwtPIWi6Y9OXK8 kDGUGrrWhJzb4gCkOMtIZQPfsrjW27ClvfJq+7ws8AiklwMvifTfoIqrvGB8+U5YMT+y /WJILg6wI9EvnU7n84UL41uwNT82WMQZT/VTrpfAGAyV4ROJJPCimYnOZwukGD/bQiD8 ewbaYZPXL6OK8qmpblf1CD7bYYJk4jhA+qlj0Uh5QcGXxVJBU5TVT0JhdjBTS2Gu4rDb Kelw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=JprEgZjDlpCy8+NMge7o9xrV3/BVYvYc48ostcdWCx0=; b=Nj50ruzqGUv8wF91oB+oK8wTQPtxXleA+VnbOeX17Q1SsscqehcJCB0zZFihJwx1Lu wlO8DujA5XbCwrGOp7G4Ht0V/UAKkr3zAOpZ8cioRLjPjWk15QIx315zxMVLpIkPWLCl LQ9VeZC7esPERc+mAjcVdSc09RsLrdgHiJHpiZHbV8E47t2LDTL+3YYmjUEiKD7SEy0x hPPJOMYDvrA6zrNJXNAGQeFLhQ635Aw9/tdwds0mz4yqExGkt8qVC31de/oCUQAjNgCP dixmaxnHFH+O+291ez5QlzaGuKGCWnn8Z00GksZUtF+6HqKcFk1mrFNXZjImWrrrUnQT NFaA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k17si3912325ejz.227.2019.09.19.01.25.48; Thu, 19 Sep 2019 01:26:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731882AbfISIX5 (ORCPT + 99 others); Thu, 19 Sep 2019 04:23:57 -0400 Received: from mx2.suse.de ([195.135.220.15]:46080 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730886AbfISIX5 (ORCPT ); Thu, 19 Sep 2019 04:23:57 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 720C0AFA8; Thu, 19 Sep 2019 08:23:55 +0000 (UTC) Date: Thu, 19 Sep 2019 10:23:54 +0200 From: Michal Hocko To: Lin Feng Cc: corbet@lwn.net, mcgrof@kernel.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, keescook@chromium.org, mchehab+samsung@kernel.org, mgorman@techsingularity.net, vbabka@suse.cz, ktkhai@virtuozzo.com, hannes@cmpxchg.org, willy@infradead.org, kbuild test robot Subject: Re: [PATCH] [RESEND] vmscan.c: add a sysctl entry for controlling memory reclaim IO congestion_wait length Message-ID: <20190919082354.GC15782@dhcp22.suse.cz> References: <20190918095159.27098-1-linf@wangsu.com> <20190918122738.GE12770@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 19-09-19 09:32:48, Lin Feng wrote: > > > 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 > > 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 ' This would be normally the case for a patch which only fixes the particular issue. You can credit the bot in the changelog while documenting changes between version. -- Michal Hocko SUSE Labs