From: Alexey Dobriyan <adobriyan@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Contribution to Linux Kernel
Date: Fri, 10 Jun 2005 15:11:42 +0000 [thread overview]
Message-ID: <200506101911.42899.adobriyan@gmail.com> (raw)
In-Reply-To: <20050610143249.48824.qmail@web8604.mail.in.yahoo.com>
On Friday 10 June 2005 18:32, Latha D wrote:
> I have strong desire to work and contribute to Linux
> kernel. Could anyone please help me by guiding me and
> providing work items to do?
From Dave Jones:
One of my interests is static code analysis. As the Linux kernel
continues to grow at an exponential rate, I believe we need more (and
better) tools to catch bugs before they become a problem. It seems I'm
not alone in this thinking. I stumbled across a whole slew of debugging
tools on Microsoft's developer site, by the names of PREfast, SDV and
Driver Verifier.
http://www.livejournal.com/users/kernelslacker/15681.html
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-06-10 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 14:32 [KJ] Contribution to Linux Kernel Latha D
2005-06-10 15:07 ` walter harms
2005-06-10 15:11 ` Alexey Dobriyan [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=200506101911.42899.adobriyan@gmail.com \
--to=adobriyan@gmail.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.