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 12:34:21 +0800 [thread overview]
Message-ID: <524267CD.4030007@asianux.com> (raw)
In-Reply-To: <52424094.3020504@asianux.com>
On 09/25/2013 09:47 AM, Chen Gang wrote:
> On 09/25/2013 09:14 AM, Tejun Heo wrote:
>> On Wed, Sep 25, 2013 at 09:06:52AM +0800, Chen Gang wrote:
>>> 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 :-(.
>>
>> Yeah, at least partly. That and the fact that I'm not too willing to
>> dig into the code without further evidence. It isn't anything strange
>> to ask tho and I'm likely to do that even for subsystems that I know
>> intimately if the subject code has been stable / stale for years and
>> the analysis doesn't seem immediately convincing. And, if my
>> experience is anything to go by, it's not too unlikely that you might
>> hit something which doesn't agree with your current assumptions while
>> trying to actually trigger the problem.
>>
>> Thanks.
>>
>
Excuse me, I have to do some urgent internal things within my company,
so the test and confirmation may be delayed (I will try to finish test
within this month: 2013-09-30).
> Excuse me, my English is not quite well, I do not quite understand what
> you said (but it seems what you said is reasonable, and not need reply).
>
>
> Thanks.
>
--
Chen Gang
next prev parent reply other threads:[~2013-09-25 4:35 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
2013-09-25 1:14 ` Tejun Heo
2013-09-25 1:47 ` Chen Gang
2013-09-25 4:34 ` Chen Gang [this message]
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=524267CD.4030007@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