All of lore.kernel.org
 help / color / mirror / Atom feed
From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Newbie help
Date: Tue, 04 Aug 2015 10:21:15 +0200	[thread overview]
Message-ID: <87k2tbcvlw.fsf@nemi.mork.no> (raw)
In-Reply-To: <55BF7CDA.80401@gmail.com> (Rishabh Chakrabarti's message of "Mon, 3 Aug 2015 14:38:18 +0000")

Rishabh Chakrabarti <bassdeveloper@gmail.com> writes:

> Hello all,
>
> Where can I search the archives and other resources for answering the
> following questions:
> 	
> 1. How to dive into the code? i.e. entry points

Wherever your interest is. There are no strict rules.  If you don't know
ahere your interest is, then you should ask yourself why you are
interested in the Linux kernel in the first place.

Out of your areas of interest, try to find a part of the kernel which is
well maintained and have (semi-)sufficient reviewer resources, because
you will need that as a newbie. You may use the Status field in
MAINTAINERS as an initial guide, but only recent mailing list archives
will tell for sure.  Look for comments and feedback on patches.

> 2. What are the pre-requisites for understanding the whole code?

I don't think that is possible...

You should understand the part you want to modify.  You'll need some
knowledge of C, and an ability to learn.  The latter is most important.

> 3. Best books and resource material

I see that Documentation/ and LDD3 is already mentioned. Other than
that: The source code is there, and is much more readable and commented
than most other C projects.  Use it.  Reading code, and trying to figure
out how it works and why it was written like that, is a great way to
learn.

Use the git commit messsages to help understanding if there is something
which isn't obvious (there will be, of course).  Every single commit is
justified and explained and in detail in git.  And you will have to do
the same, so you should familiarize yourself with those messages in any
case.


Bj?rn

  parent reply	other threads:[~2015-08-04  8:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 14:38 Newbie help Rishabh Chakrabarti
2015-08-03 15:23 ` Anuz Pratap Singh Tomar
2015-08-04  2:12 ` Navy Cheng
2015-08-04  6:55 ` Schrey, Moritz
2015-08-18 12:35   ` Andrey Skvortsov
2015-08-04  8:21 ` Bjørn Mork [this message]
2015-08-04  9:09   ` Manavendra Nath Manav
  -- strict thread matches above, loose matches on Subject: below --
2021-12-12 15:06 Lorenzo Mainardi
2021-12-12 16:47 ` Toke Høiland-Jørgensen
2007-10-22 18:23 newbie help Onkar
2007-10-24  9:35 ` Akio Takebe
2006-08-30 15:07 Newbie Help James Arnott
2004-05-05 17:28 Newbie help Manu Sharma

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=87k2tbcvlw.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --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.