public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Li Zefan <lizefan@huawei.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	xi.wang@gmail.com, nicolas.dichtel@6wind.com,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/sysctl_binary.c: improve the usage of return value 'result'
Date: Wed, 07 Aug 2013 14:24:05 +0800	[thread overview]
Message-ID: <5201E805.2080008@asianux.com> (raw)
In-Reply-To: <5201E192.7060108@huawei.com>

On 08/07/2013 01:56 PM, Li Zefan wrote:
>>> The right answer to the code is to config it out and then you don't have
>>> to worry about it one way or another.
>>>
>>
>> Pardon?
>>
>> Excuse me, my English is not quite well, I don't quite understand your
>> meaning, could you please repeat again in details or say more clearly ?
>>
>>
>>> The sysctl binary path has never been properly maintained and I don't
>>> intend to start.   But I will spend 5 minutes to say this patch seems to
>>> make the code worse not better.
>>>
>>
>> I guess no one ever invited you to maintain this file (for just as you
>> said, this file will be removed), so don't worry about it.
>>
>> Hmm... do you mean you spend 5 minutes to get a conclusion ? if so,
>> better not use word 'seems' which is not a suitable word appeared in
>> the results, proofs or conclusions.
>>
> 
> To be honest...
> 
> You are too bad in english to do kernel development. You don't seem to
> know how to communicate in english...
> 

So I should improve my English, and now I am just trying improving.

At least, it is not an excuse to leave upstream kernel development, is
it right ?  or do you have additional ideas or suggestions ?


> And people easily get frustrated or even pissed off when discussing with
> you. That's why tglx descided to put your emails into /dev/null...
> 

If any member won't discuss with me because of my bad English, and put
my e-mail into "/dev/null", I can understand, and say sorry to them.

So I really need thank the members who still want to discuss with me.

Do you still want to discuss with me ? if not, please put my e-mail
into "/dev/null", I really can understand, and say sorry to you.

Thanks.

>> At least, one conclusion is: this patch switches from old-style to
>> new-style, not for optimization.
>>
>> But for sysctl_getname() and "checkpatch.pl" of this patch, better to
>> get more discussion.
>>
>> Is it OK ?
> 
> 
> 


-- 
Chen Gang

  parent reply	other threads:[~2013-08-07  6:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06  7:29 [PATCH] kernel/sysctl_binary.c: improve the usage of return value 'result' Chen Gang
2013-08-06 21:43 ` Andrew Morton
2013-08-06 22:11   ` Joe Perches
2013-08-07  3:53     ` Chen Gang
2013-08-06 22:13   ` Eric W. Biederman
2013-08-07  5:28     ` Chen Gang F T
2013-08-07  5:11   ` Chen Gang
2013-08-06 21:46 ` Eric W. Biederman
2013-08-07  5:07   ` Chen Gang
2013-08-07  5:56     ` Li Zefan
2013-08-07  6:10       ` Joe Perches
2013-08-07  6:29         ` Chen Gang
2013-08-07  6:42         ` Li Zefan
2013-08-07  6:42         ` Li Zefan
2013-08-07  6:57           ` Chen Gang
2013-08-07  6:24       ` Chen Gang [this message]
2013-08-07  6:29         ` Andrew Morton
2013-08-07  6:34           ` Chen Gang
2013-08-07  7:02         ` Li Zefan
2013-08-07  8:03           ` Chen Gang
2013-08-07  8:44             ` Li Zefan
2013-08-07  9:13               ` Chen Gang
2013-08-07  7:45     ` Eric W. Biederman
2013-08-07 10:25       ` Chen Gang
2013-08-07 18:38         ` Eric W. Biederman
2013-08-08  3:19           ` 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=5201E805.2080008@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=nicolas.dichtel@6wind.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xi.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox