From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Beyond kernel-janitor
Date: Fri, 15 Feb 2013 10:43:59 -0800 [thread overview]
Message-ID: <20130215184358.GA3244@gmail.com> (raw)
Hi All,
After watching Greg's video on "How to write and submit your first patch",the
discussions that happened over kernel newbie mailing list and the assorted
information scattered in the kernel Documentation directory, I was able to set
up my Linux box for sending janitorial related patches (mostly checkpatch.pl
cleanup) [1] and I'm happy that some of those got merged in the upstream kernel
I'd like to contribute even more and I was wondering how to proceed further.
My work experience has been mostly in the computer network domain, so I think
I've somewhat high level view of the Linux networking subsystem, but I do not
know the exact areas where I should concentrate. For a beginner like me, trying
to start at the core network elements is daunting. On the other hand, I do not
have a networking device for which I can try to come up with a minimal device
driver. Therefore In order to concentrate my work on Network subsystem of Linux,
what should be the possible entry points for me. I'm planning to get myself this
book [2] on Linux Network Internals. While this would take a while for me to
digest all the stuff, are there any other places where I can just Jumpstart ?
[1] http://marc.info/?a=135084530900004&r=1&w=2
[2] http://shop.oreilly.com/product/9780596002558.do
Looking forward for your suggestions.
-Amit
next reply other threads:[~2013-02-15 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 18:43 Kumar amit mehta [this message]
2013-02-15 20:10 ` Beyond kernel-janitor Kevin Wilson
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=20130215184358.GA3244@gmail.com \
--to=gmate.amit@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 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.