public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Valdis.Kletnieks@vt.edu, Greg KH <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Consult] Plan: personal contributes plan for 2013
Date: Sat, 26 Jan 2013 16:17:01 +0800	[thread overview]
Message-ID: <510390FD.6050206@gmail.com> (raw)
In-Reply-To: <5101EE2B.3080004@asianux.com>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

Hello all:

Opinion:
  after think of again, for "10 patches per month":
  I think in kernel wide, it is not quite hard to perform.

Finished:
  currently (within Jan 2013)
    in next-20130125 tree, can find about 11 patches of mine.
      patch contents: usb, staging, tty sub-systems, ...
      patch type:     1 for MAINTAINER, 1 for beautify code,
                      others for memory override or resource management.
      marked as:      9 for Signed-of-by, 2 for Reported-by
    (please use "git log", then search "Chen Gang" to get details)
    (also, I do it in part time in Jan 2013)

Ways:
  for memory override:
    A) search strcpy, strncpy, sprintf, and memcpy in kernel wide
    B) we will get more than 10,000 lines (maybe almost 100,000 lines).
    C) then see each of them.
    in my experience (statistic): can find a bug per 10 lines.

  for resource management:
    A) at least, we can search 'kfree' in kernel wide
    B) we will get more than 10,000 lines (maybe almost 100,000 lines).
    C) then see each of them.
    in my experience (statistic): can find a bug per 100 lines.

Hope:
  if most of my patches are qualified both for "Accept" and for "Quality"

    I hope to share this simple way to every one.
    so that, most of us can provide more valuable patches in this simple way.

  else (most of my patches are not qualified)

    please give reasons.
    if really they are, I should notice next time (also need adjust my plan)


  thanks


-- 
Chen Gang

Flying Transformer

[-- Attachment #2: chen_gang_flying_transformer.vcf --]
[-- Type: text/x-vcard, Size: 67 bytes --]

begin:vcard
fn:Chen Gang
n:;Chen Gang
version:2.1
end:vcard


  reply	other threads:[~2013-01-26  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 11:32 [Consult] Plan: personal contributes plan for 2013 Chen Gang
2013-01-23 14:23 ` Greg KH
2013-01-24  1:13   ` Chen Gang
2013-01-24 23:31 ` Valdis.Kletnieks
2013-01-25  2:14   ` Theodore Ts'o
2013-01-25  2:30     ` Chen Gang
2013-01-26  8:17       ` Chen Gang F T [this message]
2013-01-25  2:15   ` 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=510390FD.6050206@gmail.com \
    --to=chen.gang.flying.transformer@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=gang.chen@asianux.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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