From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-f199.google.com (mail-it1-f199.google.com [209.85.166.199]) by kanga.kvack.org (Postfix) with ESMTP id 3E8EE6B000D for ; Wed, 24 Oct 2018 02:26:21 -0400 (EDT) Received: by mail-it1-f199.google.com with SMTP id v13-v6so3867468itc.4 for ; Tue, 23 Oct 2018 23:26:21 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0049.hostedemail.com. [216.40.44.49]) by mx.google.com with ESMTPS id k3-v6si2727146ite.86.2018.10.23.23.26.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 23:26:20 -0700 (PDT) Message-ID: <0e1fc40af360ed55fd32784f6973af5940232f99.camel@perches.com> Subject: Re: [PATCH] mm: convert totalram_pages, totalhigh_pages and managed_pages to atomic. From: Joe Perches Date: Tue, 23 Oct 2018 23:26:16 -0700 In-Reply-To: <20181024061546.GY18839@dhcp22.suse.cz> References: <1540229092-25207-1-git-send-email-arunks@codeaurora.org> <15247f54-53f3-83d4-6706-e9264b90ca7a@yandex-team.ru> <7a4fcbaee7efb71d2a3c6b403c090db4@codeaurora.org> <20181024061546.GY18839@dhcp22.suse.cz> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko , Arun KS Cc: Kees Cook , Konstantin Khlebnikov , LKML , linux-mm , Minchan Kim , Arun Sudhilal , Greg Kroah-Hartman , Andrew Morton On Wed, 2018-10-24 at 08:15 +0200, Michal Hocko wrote: > On Wed 24-10-18 10:47:52, Arun KS wrote: > > On 2018-10-24 01:34, Kees Cook wrote: > [...] > > > Thank you -- I was struggling to figure out the best way to reply to > > > this. :) > > I'm sorry for the trouble caused. Sent the email using, > > git send-email --to-cmd="scripts/get_maintainer.pl -i" > > 0001-convert-totalram_pages-totalhigh_pages-and-managed_p.patch > > > > Is this not a recommended approach? > > Not really for tree wide mechanical changes. It is much more preferrable > IMHO to only CC people who should review the intention of the change > rather than each and every maintainer whose code is going to be changed. > This is a case by case thing of course but as soon as you see a giant CC > list from get_maintainer.pl then you should try to think twice to use > it. If not sure, just ask on the mailing list. Generally, it's better to use scripts to control the --to-cmd and --cc-cmd options. Something like what I detailed here: https://lkml.org/lkml/2016/9/14/482