From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Introduction and getting started...
Date: Wed, 18 Jul 2012 13:43:20 +0000 [thread overview]
Message-ID: <20120718134320.GA16291@mwanda> (raw)
In-Reply-To: <20120718133104.GH2879@mcpierce-laptop.rdu.redhat.com>
On Wed, Jul 18, 2012 at 09:31:04AM -0400, Darryl L. Pierce wrote:
> Hi, everybody. I'm fairly new to this mailing list (just signed up last
> week) and want to start contributing in some fashion to Linux kernel
> development. But I'm not sure where or how to get started. So I'm asking
> for some advice: point me to a FAQ or guide for pitching in, please.
>
> Thanks in advance.
The best way to start is just to fix bugs. Try compiling the kernel
with the "clang" static checker stuff. It should find some
potential bugs. Sort through them and find which are real. Then
fix them.
I don't think anyone is using the clang checker on a regular basis.
Run it against linux-next.
The key really is to read a lot of code and find bugs.
regards,
dan carpenter
next prev parent reply other threads:[~2012-07-18 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 13:31 Introduction and getting started Darryl L. Pierce
2012-07-18 13:43 ` Dan Carpenter [this message]
2012-07-18 14:02 ` Darryl L. Pierce
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=20120718134320.GA16291@mwanda \
--to=dan.carpenter@oracle.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.