kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: danielhamacher.dh@gmail.com (Daniel Hamacher)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Getting started on Linux Kernel Development
Date: Fri, 31 May 2013 11:55:51 -0600	[thread overview]
Message-ID: <51A8E427.7030809@gmail.com> (raw)

Greetings.

My name is Daniel and I am starting out in Linux Kernel development on a 
Debian Linux distribution. I followed the steps on kernelnewbies.org and 
I am booting now with 3.10.0-rc3+. So I build the compiler and I am also 
booting from it. I watched the video from Greg Kroah-Hartman on how to 
submit patches, I created a branch, so I am ready to go...

How do I get started with the Kernel janitors to get my feet wet? I have 
intermediate knowledge of C and basic knowledge of Assembly. Is there 
anything in particular that I can get started on? Thanks.


Cheers,
Daniel

             reply	other threads:[~2013-05-31 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 17:55 Daniel Hamacher [this message]
2013-05-31 19:05 ` Getting started on Linux Kernel Development Denis Kirjanov
2013-05-31 19:23   ` Jonathan Neuschäfer
2013-06-02 10:43 ` Bjørn Mork
2013-06-03 16:03   ` 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=51A8E427.7030809@gmail.com \
    --to=danielhamacher.dh@gmail.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).