public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] kernel/groups.c: consider about NULL for 'group_info' in all related extern functions
Date: Wed, 25 Sep 2013 09:06:52 +0800	[thread overview]
Message-ID: <5242372C.4010509@asianux.com> (raw)
In-Reply-To: <20130925005802.GA25777@htj.dyndns.org>

On 09/25/2013 08:58 AM, Tejun Heo wrote:
> Hello, Chen.
> 
> On Wed, Sep 25, 2013 at 08:49:31AM +0800, Chen Gang wrote:
>>> Can you please demonstrate such failure?  You can tell kernel to
>>> execute a given binary instead of init with "init=" param.
>>
>> OK, I will/should try, today (although I have to spend my additional
>> time resource on it. :-( ).
> 
> Please note that that's not necessarily "additional" resource that you
> spend.  It's more of something necessary to justify the changes you're
> suggesting.  It's true that not all bug fixes / improvements require
> explicit demonstration but I'm not very convinced about your analysis
> partly because I'm not too familiar with the code path but also
> because the code has been stable with years and you seem pretty new to
> the area.
> 
>> Hmm... in fact, in my opinion, interface (especially content system
>> call) need make itself consistency, although at present, it can not
>> cause issue.
> 
> Sure, it should be consistent but I'm not sure what you're perceiving
> as inconsistent is actually inconsistent.  Anyways, let's please have
> something deomnstratable.  We can think more about the interface
> niggles afterwards.
> 
> Thanks.
> 

OK, I see, the 'root cause' is: "you are not the related maintainer
either", so it is really necessary for me to spend additional time
resource on it :-(.

But all together, thank you for spending your time resource on it, let
us continue :-).


Thanks.
-- 
Chen Gang

  reply	other threads:[~2013-09-25  1:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  3:01 [PATCH] kernel/groups.c: consider about NULL for 'group_info' in all related extern functions Chen Gang
2013-08-20  3:03 ` Chen Gang
2013-09-03  5:23   ` Chen Gang
2013-09-23 15:06 ` Tejun Heo
2013-09-24  3:42   ` Chen Gang
2013-09-24  4:06     ` Tejun Heo
2013-09-24  4:27       ` Chen Gang
2013-09-24 12:04         ` Tejun Heo
2013-09-25  0:49           ` Chen Gang
2013-09-25  0:58             ` Tejun Heo
2013-09-25  1:06               ` Chen Gang [this message]
2013-09-25  1:14                 ` Tejun Heo
2013-09-25  1:47                   ` Chen Gang
2013-09-25  4:34                     ` Chen Gang
2013-09-26  5:58                       ` Chen Gang
2013-09-26  6:30                         ` Chen Gang
2013-09-26 13:15                           ` Tejun Heo
2013-09-27  1:30                             ` Chen Gang
2013-09-27  3:36                               ` Tejun Heo
2013-09-27  7:16                                 ` Chen Gang
2013-09-27 11:53                                   ` Tejun Heo
2013-09-27 12:19                                     ` Chen Gang
2013-09-29  2:50                                       ` 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=5242372C.4010509@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=tj@kernel.org \
    /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