Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3001742ybt; Mon, 29 Jun 2020 12:35:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzr4M/atV6VDU9c6PC+ABNbH6Dz4nuEMKw/7QKmYV4WVhr+QQv9mnUcKa6WXP54wVEkm/f/ X-Received: by 2002:a17:906:1356:: with SMTP id x22mr15948036ejb.429.1593459304912; Mon, 29 Jun 2020 12:35:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593459304; cv=none; d=google.com; s=arc-20160816; b=D+CLM/6/fO0ICamRCnDd4pEUBr3oNmcAz/HOYoEEt7PWLL31E49ffyz3Df3MQTu6is RxQTRQzs9P5OpY4kEEpQ0Y/owVUVHc5waHER4j9686yx5Z3tX4Xagrdo8BvZszXu5bCW SkFt6vs4Di7F7BewQA8PNtO2Ppipd5GHJX0WtTDhZaBJjSSaokU2D8Pt9lHFELoZ9DLz WZp1yGre1/XsLQVJf93BImIonVVbo5M5IKHr5p99g2Cj0NYBRkESvd1yyMLuD6Bjcwmu vvzxaQgO1tphQeD6AhNbNx/OMPDTRMJcIIXLmHYl19WmfphzTCC2dH5bt2P3aGhhCaKj Se6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=iuUtv6v1SnkZsKjkQAh2b6D5UYYnPXkjBt8FcDC4EwU=; b=GJy4R//uP5RDG2VM6KVR57UE1vgr4mXjtQAtGV93HB9Ki9X9sUX/ZwfXuG1b6X+SU6 8yvGI3wtHX6sGKQw7R8wRFr1XW+TQjuuMgnX+MkRyfJUzwRbohbZzFodWvD5V/WUOQec Dw+oicd8h/p6FBsEMGXWLa7c87WbuD0cSfTacZGAwI5GG3RBoizKbUaXEu3TQ7v3V9tq 7ruStSMfG7BNw5T3smEydSYLbYD6yXCbbzE12VLGF9WCpQ7z5Cfbc7fIDvxahcx9fJ5Y 3yjrYnmgkarW8rE2N+mvtnqai2fSoDNF/H/VEPQ0U+XYBmjd+aOw6bXZhjuqEVK1YB3i XPPA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cm10si251699edb.208.2020.06.29.12.34.42; Mon, 29 Jun 2020 12:35:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731272AbgF2Tei (ORCPT + 99 others); Mon, 29 Jun 2020 15:34:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:36738 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733155AbgF2Tb0 (ORCPT ); Mon, 29 Jun 2020 15:31:26 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id EA306AF39; Mon, 29 Jun 2020 07:13:38 +0000 (UTC) Date: Mon, 29 Jun 2020 09:13:38 +0200 From: Daniel Wagner To: Dave Hansen Cc: Dave Hansen , linux-kernel@vger.kernel.org, linux-mm@kvack.org, ben.widawsky@intel.com, alex.shi@linux.alibaba.com, tobin@kernel.org, cl@linux.com, akpm@linux-foundation.org, stable@kernel.org Subject: Re: [PATCH] mm/vmscan: restore zone_reclaim_mode ABI Message-ID: <20200629071338.m4veigbp4tu45gbz@beryllium.lan> References: <20200626003459.D8E015CA@viggo.jf.intel.com> <20200626075918.dj6ioaon5iuhtg6k@beryllium.lan> <83731eeb-1f64-50b7-41e9-5b7114678533@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83731eeb-1f64-50b7-41e9-5b7114678533@intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Dave, On Fri, Jun 26, 2020 at 06:53:33AM -0700, Dave Hansen wrote: > Was there something else specifically in the documentation which you > think I've neglected? The first paragraph explains how you ended up modifying the code. While I understand that you want to document the process, it wont help a reader in future. It doesn't add any intersting information at all. Just state what you're doing as first thing and explain why you are doing it after it. > > I think the documentation update should not be part of this patch. > > This makes the back porting to stable more difficult. > > Really? If a backporter doesn't care about documentation, I'd just > expect them to see the reject, ignore it, and move on with their life. > If they do, they'd want the code fix and the Documentation/ update in > the same patch so that they don't get disconnected. I understood you are fixing a regression ingroduced by a previous change. In this case I would only fix the regression. Updating/improving the documentation is good, I just don't think it's necessary to back port it to stables trees along side the bug fix. Thanks, Daniel