From: Li Zefan <lizefan@huawei.com>
To: Yong Zhang <yong.zhang@windriver.com>
Cc: <ralf@linux-mips.org>, <huawei.libin@huawei.com>,
<linux-mips@linux-mips.org>, <linux-kernel@vger.kernel.org>,
Xinwei Hu <huxinwei@huawei.com>
Subject: Re: [PATCH V2] MIPS: change type of asid_cache to unsigned long
Date: Tue, 27 May 2014 12:56:42 +0800 [thread overview]
Message-ID: <53841B0A.1030404@huawei.com> (raw)
In-Reply-To: <20140527043433.GA16193@pek-yzhang-d1>
On 2014/5/27 12:34, Yong Zhang wrote:
> On Tue, May 27, 2014 at 12:16:30PM +0800, Li Zefan wrote:
>> I'm not quite happy about what happaned here. There's a story behind
>> this patch.
>>
>> One of our Huawei product encountered a bug, and they're using WindRiver4,
>> so the kernel is 2.6.34.
>>
>> Because they bought your licnece, they asked for your help, but
>> you were reluctant on this issue, and the problem remained there
>> for about one month.
>>
>> At last they turned to us for help. We're the kernel department in
>> Huawei, but maintaining this product kernel isn't our job. Still
>> Li Bin devoted his time to analyzing this bug, and he did a great
>> job.
>>
>> Li Bin told the product team what was wrong and was about to send
>> a fix for upstream kernel.
>
> You have time to do that but you didn't.
>
Hah yeah, we do have time. we spent lots of time analyzing the bug,
and we were taking our time to write good changelog. As I've pointed
out that your changelog isn't informative.
>> They told you our analysis for further
>> confirmation,
>
> So you realy didn't make the patch, right? Because you are not
> sure the right fix.
>
We're confident about our analysis and we know how to fix it.
It's the product team wasn't sure about this, and they wasn't
able to contact with Li Bin for confirmation at that time, so they
asked you.
>> and you were so reluctant to help but so quick to
>> send the fix.
>
> We have responsed to you.
>
You responded to us but you did nothing to help, that's why the
product team found us.
>>
>> Li Bin never reported this bug, but he fixed it. It's a shame that
>> you took the credit from us.
>
> I just saw a bug report and ananysis. And I agreed and confirmed it's
> a bug.
>
And that's our work and our credit, and I don't think you're gonna
to deny it.
next prev parent reply other threads:[~2014-05-27 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 5:36 [PATCH V2] MIPS: change type of asid_cache to unsigned long Yong Zhang
2014-05-27 4:16 ` Li Zefan
2014-05-27 4:34 ` Yong Zhang
2014-05-27 4:56 ` Li Zefan [this message]
2014-05-27 4:50 ` Yong Zhang
2014-05-27 5:07 ` Li Zefan
2014-05-27 5:23 ` Yong Zhang
2014-05-27 5:52 ` Li Zefan
2014-05-28 20:09 ` Aaro Koskinen
2014-05-29 8:57 ` Li Zefan
2014-05-29 10:20 ` Ralf Baechle
2014-05-30 7:08 ` Libin
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=53841B0A.1030404@huawei.com \
--to=lizefan@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=huxinwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yong.zhang@windriver.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