From: cxie@redhat.com (Madper Xie)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Selecting a Linux Kernel Bug
Date: Mon, 24 Mar 2014 14:27:08 +0800 [thread overview]
Message-ID: <87siq8xgar.fsf@redhat.com> (raw)
In-Reply-To: <CAGUYZuTbb5BVEuwQRZdf5qAD=Xs7xBkfqvLBR9ZDwG+2xq3_EA@mail.gmail.com>
sanjeev sharma <sanjeevsharmaengg@gmail.com> writes:
> Hi Greg
>
> Where Kernel Bugs are getting tracked? ? so that open Bugs in Kernel can be
> looked.
>
Not very sure. maybe:
https://bugzilla.kernel.org/describecomponents.cgi
I always report bugs to LKML or related mail-list. (E.g. Linux-efi)
So you'd better subscribe them.
> Regards
> Sanjeev Sharma
>
> On Wed, Mar 19, 2014 at 9:55 PM, Greg KH <greg@kroah.com> wrote:
>
> 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
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
Sent with my mu4e
next prev parent reply other threads:[~2014-03-24 6:27 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
2014-03-24 6:16 ` sanjeev sharma
2014-03-24 6:27 ` Madper Xie [this message]
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=87siq8xgar.fsf@redhat.com \
--to=cxie@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).