kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: About Low Hanging Fruits
Date: Mon, 13 Jul 2015 13:09:20 -0400	[thread overview]
Message-ID: <10024.1436807360@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 13 Jul 2015 12:13:28 +0530." <CAGYCq6gnW5agYNdK_ii1qzrbXNvv_Tp+_E=KK+4c6tDR-3UDgw@mail.gmail.com>

On Mon, 13 Jul 2015 12:13:28 +0530, Mayur Patil said:

>   I just want to know like other Open source projects is there a thing in
> linux kernel as Low hanging fruits.

The Linux kernel has been worked over by professional programmers for more
than a decade, and as a result the number of things that can be attacked
by a relatively unskilled newcomer is fairly low.

Your best place to start is probably under drivers/staging, where we put
all the stuff that's *not* up to standards yet.  Each driver should have
a TO-DO file describing what needs doing, and Greg HK is always willing to
take checkpatch style fixups for the staging tree (many other maintainers
*don't* want style patches that aren't connected to other work - if there's
other active work, they can introduce merge conflicts, and if nobody's working
on something, it's best to not touch stable code...)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150713/9a44bbfd/attachment.bin 

  reply	other threads:[~2015-07-13 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  6:43 About Low Hanging Fruits Mayur Patil
2015-07-13 17:09 ` Valdis.Kletnieks at vt.edu [this message]
2015-07-13 17:11   ` Robert P. J. Day
2015-07-14 19:37     ` Valdis.Kletnieks at vt.edu

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=10024.1436807360@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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).