[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53D1CD4C.90507@gmail.com>
Date: Fri, 25 Jul 2014 11:21:48 +0800
From: Chen Gang <gang.chen.5i5j@...il.com>
To: Nick Krause <xerofoify@...il.com>
CC: Richard Weinberger <richard@....at>,
Richard Weinberger <richard.weinberger@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Harvey Harrison <harvey.harrison@...il.com>,
Måns Rullgård <mans@...sr.com>,
Greg KH <gregkh@...uxfoundation.org>,
John Stultz <john.stultz@...aro.org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Wei Yongjun <yongjun_wei@...ndmicro.com.cn>,
Dan Carpenter <dan.carpenter@...cle.com>,
tomas.winkler@...el.com,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: Change kzalloc to kcalloc
On 07/25/2014 11:13 AM, Nick Krause wrote:
> On Thu, Jul 24, 2014 at 11:09 PM, Chen Gang <gang.chen.5i5j@...il.com> wrote:
>>
>>
>> On 07/25/2014 10:53 AM, Nick Krause wrote:
>>> On Thu, Jul 24, 2014 at 10:47 PM, Chen Gang <gang.chen.5i5j@...il.com> wrote:
>>>>
>>>>
>>>> On 07/25/2014 10:20 AM, Nick Krause wrote:
>>>>> On Thu, Jul 24, 2014 at 10:15 PM, Chen Gang <gang.chen.5i5j@...il.com> wrote:
>>>>>>
>>>>>> Excuse me, I did not see the patch details, but I guess it is about
>>>>>> whether welcome a new member to upstream kernel. For me, I have 3 ideas
>>>>>> about it if I am a newbie or a normal kernel developer:
>>>>>>
>>>>>> - Do I have enough basic skills for it?
>>>>>>
>>>>>> - Do I developed one or more another real world projects with C?
>>>>>> (they are successful projects -- at least, not failure projects)
>>>>>>
>>>>>> - Can I construct related develop environments to support what I do?
>>>>>> (e.g. building and testing for upstream kernel)
>>>>>>
>>>>>> - Am I familiar the basic working flow about kernel mailing list.
>>>>>> (e.g. format-patch, sending patch, email client configuration...).
>>>>>>
>>>>>> - Do I have a correct attitude on it?
>>>>>>
>>>>>> - Am I careful enough?
>>>>>> (e.g. if find some details may doubt, try to check and clear them)
>>>>>> (it is always neccessary for all patches)
>>>>>>
>>>>>> - Am I try my best for it?
>>>>>> (e.g. when finish coding, try what I can do: build, run and test).
>>>>>> (it is neccessary for most cases)
>>>>>>
>>>>>> - Do I have negative effect with others?
>>>>>> (e.g. discourage the newbies, or send spam to other members ...).
>>>>>> (need always try to avoid)
>>>>>>
>>>>>> - Do I really love programming, also love open source kernel?
>>>>>>
>>>>>> - Do I love it, or I have to do it for another reason?
>>>>>> (I guess, most of gmail members in open source, love programming).
>>>>>>
>>>>>> - Do I still love programming if I am discouraged by any members?
>>>>>>
>>>>>> - Do I still love open source kernel if discouraged by any members?
>>>>>>
>>>>>>
>>>>> I have most of these skills other then developing real projects in C with other
>>>>> developers as other then the kernel I don't have must interest in C outside
>>>>> of embedded programming.
>>>>
>>>> OK, thanks. If what you said is true, for me, if you will, please still
>>>> continue for open source kernel, but really need be more careful about
>>>> the patch you made before send to open mailing list.
>>>>
>>>>
>>>> Thanks.
>>>> --
>>>> Chen Gang
>>>>
>>>> Open, share, and attitude like air, water, and life which God blessed
>>>
>>> Chen ,
>>> Thanks for helping me out here :). The true through is I don't known how to
>>> build test correctly as a newb and thought it was better just to avoid it(stupid
>>> me). I would like to known how to do this and if there is any way I can help you
>>> guys out , please let me known :). I don't want to be avoided I am honestly here
>>> to help make your life easier.
>>
>> Excuse me, my English is not quite well, I do not understand what you
>> said, I guess your meaning is "not familiar with how to build and test
>> upstream kernel" If what I guess is incorrect, please let me know.
>>
>> There are some books or some related web links for building and test
>> kernel, they are not quite difficult to get (please google search).
>>
>> I guess, it is necessary to reference these information and construct
>> related develop environments to support what you want to do next.
>>
>>
>> By the way, excuse me, today I have to do some other things firstly, so
>> maybe my next email reply will be late (may tomorrow, or the day after
>> tomorrow).
>>
>>
>> Thanks.
>> --
>> Chen Gang
>>
>> Open, share, and attitude like air, water, and life which God blessed
>
> That's what I meant. If you can sent me a link to how to do build testing
> that would be great :).
Please read README at the root directory of kernel source, also
"./Documents" contents many valuable information. And try google search
for additional information.
Try to accomplish them by yourself, that will let yourself improved with
efficiency.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists