From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Selecting a Linux Kernel Bug
Date: Wed, 19 Mar 2014 09:25:06 -0700 [thread overview]
Message-ID: <20140319162506.GA18278@kroah.com> (raw)
In-Reply-To: <CADi-0_NSVKK3gyNOBXV1U1NfZnk2qH7o4AzWkUWfvXd43cfazA@mail.gmail.com>
On Wed, Mar 19, 2014 at 09:48:13PM +0530, Ashwin Jha wrote:
>
> Hi All,
>
> I am a first year graduate student at Indian Statistical Institute, Kolkata,
> India. I have to do a small OS assignment. As I always wanted to contribute to
> Linux, I am thinking of working on a Linux kernel bug or a new feature as part
> of my assignment.
>
> I have never worked on Linux kernel before. So, I need some help for selecting
> a bug or a feature that can be resolved in a month's time. The time period is
> not strict but desired. What I really want is a problem that will help me in
> building a good understanding of Linux kernel.
How about looking at drivers/staging/*/TODO ? There's lots of things
there that need cleanups and help.
Good luck,
greg k-h
next prev parent reply other threads:[~2014-03-19 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:18 Selecting a Linux Kernel Bug Ashwin Jha
2014-03-19 16:25 ` Greg KH [this message]
2014-03-24 6:16 ` sanjeev sharma
2014-03-24 6:27 ` Madper Xie
2014-03-24 6:52 ` sanjeev sharma
2014-03-24 13:23 ` Valdis.Kletnieks at vt.edu
2014-03-26 3:10 ` Greg Freemyer
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=20140319162506.GA18278@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.