Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3006570ybt; Mon, 29 Jun 2020 12:43:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx0EZkXY7A+zXwEkW4/7SrSCGx5dg1Lgo4q++wBUWq96SAa5P7I2sj5n8rfx5xeJPbyKbB7 X-Received: by 2002:a50:c44b:: with SMTP id w11mr20132926edf.317.1593459825646; Mon, 29 Jun 2020 12:43:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593459825; cv=none; d=google.com; s=arc-20160816; b=mIrNMGok0vJsnLY6ufbglM4WC27rGYuPHJAT8TwA3NwE1T3037V+W525pk7vCiLAys WJAVkYVW4DI4EdwdT60tVbC8k7ILSR4si1LkoN+8VBH/StDft7yIaboj1o/UgtTkiCGd e4Boog88ipRe7/KrnA6O87yPbSicwD56nbCIKJN/AnyyYIdpTmLbnS3LNzf0GXScIcWL 9JUuA3GGde+DYiXv7Jl1mElQQjX9Uh/WnFO6q78fcDWIQQscppodfbPSonakCidWySYn 1KLj8TzHbxHkUnHKuzlC+Z507spo7A85egWSoslydWpjNeVx2Fpj92WpwxrkCJadFMCj gHCQ== 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=wyDxljtLmd4GZwfgQdEWQxxiQlmYgff3EO+NwlFrw7k=; b=DxpHUmImCDd8dQNulrBrvDBYaSpH+7pundT4nKcL9bVn2Fbr7JerBvax/2vKtyuPMX F2rX93z+cWjfriPox1IJazgE0aObU+EXAggSA/R7ZCFcTwfclemyosi11faSeKao0AED u4g3s6uHXc0CeMTgmUrrycnNxIE6cSs/qTlRtswYMIcHKqnibCSd/sBW+b7yFL/kGEdZ GOGLWSNLPeynRad9uVCmFLnBdRi0orR6PnbLixrIB9cUY9fUZ/41HmEz7isp18MfNf5O TwWoQEU5cIMWN/tP3P8vH0IyiPaT9PJ1cXSLKacXnEWSjnSHq8MWgBL3TMnxX7mRBJ8R D//w== 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 b19si275893edy.438.2020.06.29.12.43.22; Mon, 29 Jun 2020 12:43:45 -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 S1726875AbgF2Tl0 (ORCPT + 99 others); Mon, 29 Jun 2020 15:41:26 -0400 Received: from mx2.suse.de ([195.135.220.15]:41408 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729393AbgF2TlZ (ORCPT ); Mon, 29 Jun 2020 15:41:25 -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 37EF8AD26; Mon, 29 Jun 2020 15:53:03 +0000 (UTC) Date: Mon, 29 Jun 2020 17:53:02 +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: <20200629155302.6okkufqmj3kupvzw@beryllium.lan> References: <20200626003459.D8E015CA@viggo.jf.intel.com> <20200626075918.dj6ioaon5iuhtg6k@beryllium.lan> <83731eeb-1f64-50b7-41e9-5b7114678533@intel.com> <20200629071338.m4veigbp4tu45gbz@beryllium.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 29, 2020 at 07:36:15AM -0700, Dave Hansen wrote: > On 6/29/20 12:13 AM, Daniel Wagner wrote: > > I went to go add a new RECLAIM_* mode for the zone_reclaim_mode > > sysctl. > > This conveys my motivation. You don't need to tell a story. As explained in the documetation 'Describe your changes', describe your change in imperative mood, e.g. something like "Add RECLAIM_* mode for the the zone_reclaim_mode sysctl." > > Like a good kernel developer, I also went to go update the > > documentation. > > This takes the opportunity to throw a tiny bit of shade in the direction > of the other folks who modified the #define without updating the > documentation. What about something simple as, "Update the documetation to match the implementation" or whatever makes it clear why you are touching the documetation bits. Anyway, I just wanted to help you to write better commit messages. I understand, my help is not welcome.