From: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Chen Gang <gang.chen@asianux.com>,
lig.fnst@cn.fujitsu.com, chuansheng.liu@intel.com,
Wang YanQing <udknight@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/smp.c: free related resources when failure occurs in hotplug_cfd()
Date: Tue, 09 Jul 2013 08:25:48 +0800 [thread overview]
Message-ID: <51DB588C.8070000@gmail.com> (raw)
In-Reply-To: <20130708142605.GA2786@windriver.com>
On 07/08/2013 10:26 PM, Paul Gortmaker wrote:
> [[PATCH] kernel/smp.c: free related resources when failure occurs in hotplug_cfd()] On 08/07/2013 (Mon 16:50) Chen Gang wrote:
>
>> > When failure occurs in hotplug_cfd(), need release related resources,
>> > or will cause memory leak.
>> >
>> > Also beautify the related code.
> No. Please do not mix real fixes with trivial whitespace changes.
> It makes it harder for the reviewer to find the actual fix, and it
> makes the fix less portable to other releases (i.e. stable trees.)
>
OH, at least, need delete white spaces.
> Also, you say "beautify", but that is a matter of opinion. You
> shuffle around the tabs in your whitespace change, and yet even
> then you don't manage to adapt it to the general coding style of
> having multi-line args align with where the 1st arg starts. So
> you have done nothing but pollute the "git blame" history of that
> file for other users.
>
OK, I will send patch v2 for it (which will remove the waste
'beautifying' operation).
> You might want to slow down on the quantity of patches you send,
> and spend more time reading the comments from other people on
> reviewed patches and learning some of the implicit requirements
> from those.
No, that only means I still need improving my patch sending.
Hmm... for 'learning', I think: "learn with each other, never too old to
learn, never stop learning", so we can learn from most of patches or
replies which sent by many members.
e.g. I understand that for beautifying code, I need more consideration:
not only about coding style rules, but also the readers from 'git' and
the reviewers from 'diff'.
> I've noticed that you are already dangerously close
> to annoying several key subsystem maintainers, and that is not
> the right long term approach to working with the linux community.
If no reply, I will(of cause) no reply either.
Especially, every members' time resource is always expensive.
Thanks.
--
Chen Gang
next prev parent reply other threads:[~2013-07-09 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 8:50 [PATCH] kernel/smp.c: free related resources when failure occurs in hotplug_cfd() Chen Gang
2013-07-08 14:26 ` Paul Gortmaker
2013-07-09 0:25 ` Chen Gang F T [this message]
2013-07-09 0:28 ` Wang YanQing
2013-07-09 0:32 ` Chen Gang
2013-07-09 0:43 ` [PATCH v2] " Chen Gang
2013-07-09 0:46 ` Wang YanQing
2013-07-09 0:46 ` 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=51DB588C.8070000@gmail.com \
--to=chen.gang.flying.transformer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=gang.chen@asianux.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=udknight@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.