mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: "Richard Weinberger" <richard@nod.at>,
	"Richard Weinberger" <richard.weinberger@gmail.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Harvey Harrison" <harvey.harrison@gmail.com>,
	"Måns Rullgård" <mans@mansr.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	"John Stultz" <john.stultz@linaro.org>,
	"Paul Gortmaker" <paul.gortmaker@windriver.com>,
	"Wei Yongjun" <yongjun_wei@trendmicro.com.cn>,
	"Dan Carpenter" <dan.carpenter@oracle.com>,
	tomas.winkler@intel.com,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: Change kzalloc to kcalloc
Date: Fri, 25 Jul 2014 11:34:40 +0800	[thread overview]
Message-ID: <53D1D050.6030508@gmail.com> (raw)
In-Reply-To: <CAPDOMViMDiWONkk=TMu-U6ugKr4uiPk_km=-z-dO_0MwxYJ03w@mail.gmail.com>



On 07/25/2014 11:30 AM, Nick Krause wrote:
> On Thu, Jul 24, 2014 at 11:21 PM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>>
>>
>> On 07/25/2014 11:13 AM, Nick Krause wrote:
>>> On Thu, Jul 24, 2014 at 11:09 PM, Chen Gang <gang.chen.5i5j@gmail.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@gmail.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@gmail.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
> 
> That seems to be the issue with my programming here.

For me, constructing related environments is necessary for developers,
especially for senior developers.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2014-07-25  3:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 23:03 Nicholas Krause
2014-07-23 23:07 ` David Rientjes
2014-07-23 23:08 ` Richard Weinberger
2014-07-24 14:47 ` Steven Rostedt
2014-07-24 14:51   ` Steven Rostedt
2014-07-24 16:15     ` Måns Rullgård
2014-07-24 16:31       ` Nick Krause
2014-07-24 16:34         ` Måns Rullgård
2014-07-24 16:35           ` Nick Krause
2014-07-24 16:47             ` Måns Rullgård
2014-07-24 16:50               ` Nick Krause
2014-07-24 17:18                 ` Steven Rostedt
2014-07-24 17:30                   ` Harvey Harrison
2014-07-24 17:48                     ` Steven Rostedt
2014-07-24 18:41                       ` Nick Krause
2014-07-24 18:49                         ` Richard Weinberger
2014-07-24 18:55                           ` Nick Krause
2014-07-24 19:05                             ` Nick Krause
2014-07-24 19:11                               ` Richard Weinberger
2014-07-25  2:15                                 ` Chen Gang
2014-07-25  2:20                                   ` Nick Krause
2014-07-25  2:47                                     ` Chen Gang
2014-07-25  2:53                                       ` Nick Krause
2014-07-25  3:09                                         ` Chen Gang
2014-07-25  3:13                                           ` Nick Krause
2014-07-25  3:21                                             ` Chen Gang
2014-07-25  3:30                                               ` Nick Krause
2014-07-25  3:34                                                 ` Chen Gang [this message]
2014-07-25  3:39                                                   ` Nick Krause
2014-07-25  4:33                                                     ` 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=53D1D050.6030508@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.at \
    --cc=rostedt@goodmis.org \
    --cc=tomas.winkler@intel.com \
    --cc=xerofoify@gmail.com \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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

Powered by JetHome