All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Re: Audit return codes (Question about getting started)
Date: Wed, 20 Apr 2005 18:42:59 +0000	[thread overview]
Message-ID: <20050420184259.GC3444@us.ibm.com> (raw)
In-Reply-To: <42669D23.9010501@gmail.com>

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

* Jesse Millan <jesse.millan@gmail.com> [2005-0420 11:19:15 -0700]:

> 
> I just want to make sure that I understand the process correctly:
> 
> For example, take kalloc(). If I find instances that that the return
> value is not checked (and I have) i.e. they call kalloc() and
> automatically assume success and dereference the allocated memory
> without checking for NULL. I would insert to proper error checking,
> create the patch and mail the patch to kernel-janitors@lists.osdl.org?
> 
> Is this the process?

Generally, yes. You probably should verify the patch doesn't wrap in
your mail & applies cleanly by mailing to yourself.

Otherwise, send patches to the KJML and wait for replies.

Thanks,
Nish

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2005-04-20 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 18:19 [KJ] Re: Audit return codes (Question about getting started) Jesse Millan
2005-04-20 18:38 ` Randy.Dunlap
2005-04-20 18:42 ` Nishanth Aravamudan [this message]

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=20050420184259.GC3444@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.