linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <chengang@emindsoft.com.cn>
To: Theodore Ts'o <tytso@mit.edu>, Jianyu Zhan <nasa4836@gmail.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	trivial@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	rientjes@google.com, LKML <linux-kernel@vger.kernel.org>,
	Michal Hocko <mhocko@suse.cz>,
	Johannes Weiner <hannes@cmpxchg.org>,
	vdavydov@virtuozzo.com, Dan Williams <dan.j.williams@intel.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles
Date: Sun, 28 Feb 2016 08:21:40 +0800	[thread overview]
Message-ID: <56D23D94.50707@emindsoft.com.cn> (raw)
In-Reply-To: <20160227165301.GA9506@thunk.org>


On 2/28/16 00:53, Theodore Ts'o wrote:
> On Sat, Feb 27, 2016 at 10:32:04PM +0800, Chen Gang wrote:
>> I don't think so. Of cause NOT the "CODE CHURN". It is not correct to
>> make an early decision during discussing.
> 
> There is no discussion.  If the maintainer has NAK'ed it.  That's the
> end of the dicsussion.  Period.  See:
> 

For me, NAK also needs reasons.

And this issue is about "coding styles issue", I am not quite sure
whether trivial patch maintainer and mm maintainer are also the
maintainer for "coding styles issues".

I guess they are related with this patch, and their NAKs' reason are: mm
and trivial don't care about this coding style issue, is it correct?


> ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/trivial/template-index.html
> 
> Also note the comment from the above:
> 
>    NOTE: This means I'll only take whitespace/indentation fixes from the
>    author or maintainer.

OK, thanks, it is really one proof for us. :-)

I guess, the file above almost means: except whitespace/indentation,
trivial patches don't consider about the coding styles issues. But can
we say coding styles issues are not issues in our kernel? (I guess not)

If we can not say, I guess one of your suggestion is useful (maybe be
as your suggestion): find one suitable member (I guess I am not), run
"checkpatch -file" under "./include", and fix all reported issues.

Thanks.
-- 
Chen Gang (e??a??)

Managing Natural Environments is the Duty of Human Beings.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-02-28  0:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 22:26 chengang
2016-02-25  1:01 ` SeongJae Park
2016-02-25 14:12   ` Chen Gang
2016-02-25  8:57 ` Michal Hocko
2016-02-25 14:23   ` Chen Gang
2016-02-25 14:47     ` Michal Hocko
2016-02-25 22:17       ` Chen Gang
2016-02-25  9:27 ` Mel Gorman
2016-02-25 14:38   ` Chen Gang
2016-02-25 15:12     ` Jiri Kosina
2016-02-25 22:19       ` Chen Gang
2016-02-25 16:07     ` Mel Gorman
2016-02-25 22:29       ` Chen Gang
2016-02-25 22:39         ` Jiri Kosina
2016-02-26 14:57           ` Chen Gang
2016-02-25 23:12         ` SeongJae Park
2016-02-26 15:06           ` Chen Gang
2016-02-26  2:32         ` Jianyu Zhan
2016-02-26 15:26           ` Chen Gang
2016-02-27  2:45             ` Theodore Ts'o
2016-02-27 14:32               ` Chen Gang
2016-02-27 16:53                 ` Theodore Ts'o
2016-02-28  0:21                   ` Chen Gang [this message]
2016-02-28 13:27                     ` Mel Gorman
2016-02-28 15:28                       ` Chen Gang
2016-02-27 23:14                 ` Jiri Kosina
2016-02-28  0:47                   ` Chen Gang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56D23D94.50707@emindsoft.com.cn \
    --to=chengang@emindsoft.com.cn \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.cz \
    --cc=nasa4836@gmail.com \
    --cc=rientjes@google.com \
    --cc=trivial@kernel.org \
    --cc=tytso@mit.edu \
    --cc=vbabka@suse.cz \
    --cc=vdavydov@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox