From: navych@126.com (Navy Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Newbie help
Date: Tue, 4 Aug 2015 10:12:57 +0800 [thread overview]
Message-ID: <20150804021257.GA8635@debian> (raw)
In-Reply-To: <55BF7CDA.80401@gmail.com>
I'm newbie too. I just want to share my experience for 3 or 4 weeks.
1. Maybe there are no entry point for kernel code. Too much knowlege are
required. Do what you want and learing a subject which block you.
2. There are so many material in Documation/.
3. http://kernelnewbies.org/ is a good website.
4. Try to send some clean-up patch. You cat receive a task in
drivers/staging/xxx/TODO
5. Help other newbies here if you can
On Mon, Aug 03, 2015 at 02:38:18PM +0000, Rishabh Chakrabarti wrote:
> 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
> 2. What are the pre-requisites for understanding the whole code?
> 3. Best books and resource material
>
> Kindly keep a lay person in mind while answering.
> Please direct me to the right place and the rest i'll DIY. Thank you.
>
> Regards,
>
> Rishabh
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2015-08-04 2:12 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 [this message]
2015-08-04 6:55 ` Schrey, Moritz
2015-08-18 12:35 ` Andrey Skvortsov
2015-08-04 8:21 ` Bjørn Mork
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=20150804021257.GA8635@debian \
--to=navych@126.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 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.