From: Michal Hocko <mhocko@kernel.org>
To: Chen Gang <chengang@emindsoft.com.cn>
Cc: akpm@linux-foundation.org, trivial@kernel.org,
vdavydov@virtuozzo.com, hannes@cmpxchg.org, davem@davemloft.net,
tj@kernel.org, riel@redhat.com, linux-kernel@vger.kernel.org,
Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [PATCH trivial] include/linux/memcontrol.h: Clean up code only
Date: Fri, 10 Jun 2016 08:14:06 +0200 [thread overview]
Message-ID: <20160610061406.GA32285@dhcp22.suse.cz> (raw)
In-Reply-To: <575A0C7E.9020500@emindsoft.com.cn>
On Fri 10-06-16 08:40:30, Chen Gang wrote:
>
> On 6/9/16 23:46, Michal Hocko wrote:
[...]
> > That's being said, I appreciate an interest in making the code cleaner
> > but try to think whether these changes are actually helpful and who is
> > going to benefit from them.
> >
>
> For me, another readers can get benefit more or less from it: if read a
> simple line can know the whole thing (function work), why need we read
> multiple lines?
Yes I understand that this is a matter of taste but as I've said above.
I do not see this would add a benefit to justify the change.
If you are doing a reformating or white space cleanups always try to
think about those who want/need to dig into the history to understand
the code and this would add an additional step to get to the original
commit which is added the code. This is just wasting of time.
Now this would be much more tolerable when the code in question was a
maze but this is not the case.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-06-10 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 15:23 chengang
2016-06-09 15:46 ` Michal Hocko
2016-06-10 0:40 ` Chen Gang
2016-06-10 6:14 ` Michal Hocko [this message]
2016-06-10 8:34 ` Chen Gang
2016-06-09 17:39 ` Rik van Riel
2016-06-10 0:26 ` 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=20160610061406.GA32285@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengang@emindsoft.com.cn \
--cc=davem@davemloft.net \
--cc=gang.chen.5i5j@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tj@kernel.org \
--cc=trivial@kernel.org \
--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
all inboxes | Powered by JetHome®