From: Johannes Weiner <hannes@saeurebad.de>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Cyrill Gorcunov" <gorcunov@gmail.com>,
rdunlap@xenotime.net, tytso@mit.edu, hch@infradead.org,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
davem@davemloft.net, "Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments)
Date: Thu, 22 May 2008 03:07:48 +0200 [thread overview]
Message-ID: <87d4nf2ljv.fsf@saeurebad.de> (raw)
In-Reply-To: <9a8748490805211646s5ef93f8ey43ebbc7746fb1a3b@mail.gmail.com> (Jesper Juhl's message of "Thu, 22 May 2008 01:46:28 +0200")
Hi,
"Jesper Juhl" <jesper.juhl@gmail.com> writes:
> 2. How to find things to work on as a beginner
> ---
>
> Many people new to kernel development have a hard time finding
> projects to start out with. The kernel is a large project and it's not
> surprising that some people find it hard to work out where to begin.
>
> A good way to start is by trying to fix some bugs.
>
> There are plenty of bugs to go around and fixing bugs is a great way
> to learn since you need to understand (and thus learn) the code
> surrounding the bug in order to fix it properly, so it usually teaches
> a lot. Submitting small bug fixes is also a great way to get
> comfortable with the patch submission process.
>
> Finding bugs to fix is easy. Here are some ways to find useful work to
> do:
>
- Run a recent development kernel. If you already know an area that
might interest you, use the tree of that subsystem. Otherwise
Linus' tree. Or the -mm tree.
> - Build a bunch of 'randconfig' kernels and log the output from the
> build. Building some 10-20 randconfig kernels usually exposes plenty
> of warnings and/or errors during the build. Fixing some of those
> should keep you busy for a while.
>
> - Grep the kernel source for "FIXME", "XXX" and similar comments. They
> often describe areas of the code that has known bugs, could be
> optimized, needs review etc. Lots of work to do can be found that way.
>
> - Look through the Kernel Janitors TODO list
> (http://kernelnewbies.org/KernelJanitors/Todo) for items of interest,
> then try to fix some of the issues on the list.
>
> - Go through the kernel Bugzilla (http://bugzilla.kernel.org/) and see
> if you can fix any of the many bugs filed in it. There's a metric
> butload of bugs filed in there that need attention.
- Read the mailing list. Again, if you are interested in a specific
area, there are also subsystem-related mailing lists, check
http://vger.kernel.org/vger-lists.html.
Probably needs some rephrasing...
Hannes
next prev parent reply other threads:[~2008-05-22 1:08 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 5:58 [PATCH] Standard indentation of arguments Jianjun Kong
2008-05-21 7:19 ` Jiri Slaby
2008-05-21 11:35 ` David Newall
2008-05-21 8:34 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 8:50 ` Andrew Morton
2008-05-21 9:19 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 9:41 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 17:44 ` Andrew Morton
2008-05-21 19:45 ` Theodore Tso
2008-05-21 20:38 ` Rene Herman
2008-05-21 20:50 ` Andrew Morton
2008-05-21 21:08 ` Rene Herman
2008-05-21 21:12 ` Andrew Morton
2008-05-21 21:32 ` Rene Herman
2008-05-22 19:40 ` Jaya Kumar
2008-05-21 10:32 ` Christoph Hellwig
2008-05-21 12:09 ` Theodore Tso
2008-05-21 17:46 ` Andrew Morton
2008-05-21 18:57 ` Cyrill Gorcunov
2008-05-21 19:31 ` Andrew Morton
2008-05-21 20:10 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 21:25 ` Willy Tarreau
2008-05-21 21:44 ` Stefan Richter
2008-05-21 21:56 ` Willy Tarreau
2008-05-21 21:08 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Valdis.Kletnieks
2008-05-21 23:01 ` Adrian Bunk
2008-05-21 23:17 ` Rene Herman
2008-05-21 23:55 ` Adrian Bunk
2008-05-22 0:10 ` Rene Herman
2008-05-22 14:31 ` Adrian Bunk
2008-05-21 23:35 ` Al Viro
2008-05-22 0:38 ` Adrian Bunk
2008-05-22 1:05 ` Alan Cox
2008-05-22 16:08 ` Stefan Richter
2008-05-21 19:33 ` Randy Dunlap
2008-05-21 19:45 ` Cyrill Gorcunov
2008-05-21 19:54 ` Andrew Morton
2008-05-21 20:06 ` Jesper Juhl
2008-05-21 20:27 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments), " Jonathan Corbet
2008-05-21 20:37 ` Jesper Juhl
2008-05-21 23:46 ` Jesper Juhl
2008-05-22 0:12 ` Adrian Bunk
2008-05-22 0:32 ` Jesper Juhl
2008-05-22 1:03 ` Alan Cox
2008-05-22 14:56 ` Pavel Machek
2008-05-22 15:29 ` Arjan van de Ven
2008-05-22 0:14 ` Al Viro
2008-05-22 0:34 ` Jesper Juhl
2008-05-22 1:07 ` Johannes Weiner [this message]
2008-05-22 4:51 ` Cyrill Gorcunov
2008-05-22 5:34 ` david
2008-05-31 16:23 ` Nick Andrew
2008-05-21 19:42 ` Johannes Weiner
2008-05-21 19:47 ` Cyrill Gorcunov
2008-05-21 19:49 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 22:03 ` Al Viro
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=87d4nf2ljv.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gorcunov@gmail.com \
--cc=hch@infradead.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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