[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160225092752.GU2854@techsingularity.net>
Date: Thu, 25 Feb 2016 09:27:52 +0000
From: Mel Gorman <mgorman@...hsingularity.net>
To: chengang@...ndsoft.com.cn
Cc: trivial@...nel.org, akpm@...ux-foundation.org, vbabka@...e.cz,
rientjes@...gle.com, linux-kernel@...r.kernel.org, mhocko@...e.cz,
hannes@...xchg.org, vdavydov@...tuozzo.com,
dan.j.williams@...el.com, linux-mm@...ck.org,
Chen Gang <gang.chen.5i5j@...il.com>
Subject: Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles
On Thu, Feb 25, 2016 at 06:26:31AM +0800, chengang@...ndsoft.com.cn wrote:
> From: Chen Gang <chengang@...ndsoft.com.cn>
>
> Always notice about 80 columns, and the white space near '|'.
>
> Let the wrapped function parameters align as the same styles.
>
> Remove redundant statement "enum zone_type z;" in function gfp_zone.
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@...il.com>
NAK from me at least. From my perspective, it's preferrable to preserve
blame than go through a layer of cleanup when looking for the commit
that defined particular flags. It's ok to cleanup code at the same time
definitions change for functional or performance reasons.
--
Mel Gorman
SUSE Labs
Powered by blists - more mailing lists