[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56D06A01.3080207@emindsoft.com.cn>
Date: Fri, 26 Feb 2016 23:06:41 +0800
From: Chen Gang <chengang@...ndsoft.com.cn>
To: SeongJae Park <sj38.park@...il.com>
CC: Mel Gorman <mgorman@...hsingularity.net>, 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 2/26/16 07:12, SeongJae Park wrote:
>
> On Fri, 26 Feb 2016, Chen Gang wrote:
>
>>
>> git is a tool mainly for analyzing code, but not mainly for normal
>> reading main code.
>>
>> So for me, the coding styles need not consider about git.
>
>
> It is common to see reject of trivial coding style fixup patch here and
> there. Those patches usually be merged for early stage files that only
> few people read / write. However, for files that are old and lots of
> people read and write, those patches are rejected in usual. I mean, the
> negative opinions for this patches are usual in this community.
>
> I agree that coding style is important and respect your effort. However,
> because the code will be seen and written by most kernel hackers, the file
> should be maintained to be easily readable and writable by most kernel
> hackers, especially, maintainers. What I want to say is, we should
> respect maintainers' opinion in usual.
>
Yes we need consider about the maintainers' options.
And my another ideas are replied in the other thread, please check, and
welcome any ideas, suggestion, and completions.
Thanks.
--
Chen Gang (陈刚)
Managing Natural Environments is the Duty of Human Beings.
Powered by blists - more mailing lists