From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Don't know where to start linux kernel programming
Date: Wed, 23 Aug 2017 08:55:16 +1000 [thread overview]
Message-ID: <20170822225516.GF10531@eros> (raw)
In-Reply-To: <CAEdsRtpDkKZeWSAs4AG6z3f-MawaCYYJWN9XnpFWSnsqak23WA@mail.gmail.com>
On Tue, Aug 22, 2017 at 04:22:34PM +0530, SUNIL KHORWAL wrote:
> Hi,
> I'm new to linux kernel programming, I want to be a linux kernel hacker but
> i don't know where to start.
> Please help me.
I recently wrote some blog posts on this topic. You can check them out at
http://tobin.cc/blog
Greg is correct (as usual), there are loads of things to do in drivers/staging/*
IMHO don't bother venturing far outside of staging for a while, and definitely don't submit cleanup
patches to code outside of staging. You can safely get started learning kernel dev process patching
staging/*
Good luck,
Tobin.
prev parent reply other threads:[~2017-08-22 22:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170822105248epcas1p1dc4605938a18403f1af939a0ea7bcf14@epcas1p1.samsung.com>
2017-08-22 10:52 ` Don't know where to start linux kernel programming SUNIL KHORWAL
2017-08-22 11:14 ` Kamil Konieczny
2017-08-22 11:15 ` SUNIL KHORWAL
2017-08-22 22:52 ` Tobin C. Harding
2017-08-22 16:48 ` Cindy-Sue Causey
2017-08-22 16:59 ` valdis.kletnieks at vt.edu
2017-08-22 17:39 ` Greg KH
2017-08-23 15:36 ` Umair Khan
2017-08-23 22:57 ` Greg KH
2017-08-25 2:34 ` Tobin C. Harding
2017-08-23 20:08 ` Ruben Safir
2017-08-23 22:56 ` Greg KH
2017-08-22 23:26 ` Greg Freemyer
2017-08-23 9:34 ` Ruben Safir
2017-08-23 12:24 ` Daniel.
2017-08-23 23:46 ` Greg Freemyer
2017-08-24 0:03 ` Ruben Safir
2017-08-24 0:23 ` Greg Freemyer
2017-08-24 0:46 ` Greg KH
2017-08-24 1:56 ` Ruben Safir
2017-08-22 15:04 ` valdis.kletnieks at vt.edu
2017-08-22 22:55 ` Tobin C. Harding [this message]
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=20170822225516.GF10531@eros \
--to=me@tobin.cc \
--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.