linux-kernel - Re: [PATCH] staging: Change kzalloc to kcalloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53D1C526.9040307@gmail.com>
Date:	Fri, 25 Jul 2014 10:47:02 +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 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
--
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/