LKML Archive on
help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <>
To: Cong WANG <>
Cc: Russ Meyerriecks <>,,
	Andrew Morton <>
Subject: Re: Student Project Ideas
Date: Thu, 29 Mar 2007 22:59:36 +0200	[thread overview]
Message-ID: <20070329205935.GB13541@Ahmed> (raw)
In-Reply-To: <>

On Thu, Mar 29, 2007 at 06:32:21PM +0800, Cong WANG wrote:
> 2007/3/29, Russ Meyerriecks <>:
> >Hi all,
> >  I've been hacking on the Linux kernel all semester for my OS:
> >Internals class. We are given full autonomy in picking our final
> >programming project and I would love for mine to be /useful/ for the
> >Linux kernel and not just a theoretical exorcise. If anybody has any
> >bug fixes or features maybe they never got around to, and would be
> >suitable for this situation, I would love to hear about them.
> >
> First, I think you can read the book named "Kernel Projects for
> Linux". It's a good book although it's outdated.
> Second, in fact, I am also a college student and also want to find a
> suitable and real task in linux kernel for me to work on. KJ doesn't
> help much. ;-p

No, it really helps alot, just be _patient_. For me, I sent a series of dumb
patches at first to use ARRAY_SIZE macro instead of manual computation. Though
the patches were completely braindead, I learnt alot of stuff about how
everything works here. 

Beside sending this KJ patches, I keep reading from Understanding Linux kernel v3
and reading lots of code everyday. Yesterday my first semi-real patch was
accepted in -mm. I'm sure that day by day my patches will be more real and fix
serious issues. 

All of that wouldn't have smoothly happened without the first step, the KJ step ;).

It seems that being a developer in the kernel community is going exactly like how
code goes, _evolution_ not a revolution. You can't be responsible for a good
project directly, just take your way from a janitor to a subsystem maintaner :).
Ofcourse, unless you have an old experience in other OSs (espcifically Unix ones).


Ahmed S. Darwish

  reply	other threads:[~2007-03-29 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 10:04 Russ Meyerriecks
2007-03-29 10:15 ` Helge Hafting
2007-03-29 10:32 ` Cong WANG
2007-03-29 20:59   ` Ahmed S. Darwish [this message]
2007-03-29 22:54     ` Kyle Moffett
2007-03-30  0:09       ` Jan Engelhardt
2007-03-30  0:25         ` Kyle Moffett
2007-03-29 16:35 ` Stefan Richter
2007-03-29 20:44 ` Ahmed S. Darwish
2007-03-30  5:17 ` Lee Revell
2007-03-30 15:34 ` Pavel Machek
2007-03-30 16:15   ` Gerb Stralko
2007-04-02 13:01     ` Pavel Machek

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070329205935.GB13541@Ahmed \ \ \ \ \ \
    --subject='Re: Student Project Ideas' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox