[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0e1fc40af360ed55fd32784f6973af5940232f99.camel@perches.com>
Date: Tue, 23 Oct 2018 23:26:16 -0700
From: Joe Perches <joe@...ches.com>
To: Michal Hocko <mhocko@...nel.org>, Arun KS <arunks@...eaurora.org>
Cc: Kees Cook <keescook@...omium.org>,
Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, Minchan Kim <minchan@...nel.org>,
Arun Sudhilal <getarunks@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] mm: convert totalram_pages, totalhigh_pages and
managed_pages to atomic.
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
Powered by blists - more mailing lists