From: Dinolinux <slackfan@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Need to get some very basic things sorted out
Date: Wed, 28 Sep 2005 15:14:22 +0000 [thread overview]
Message-ID: <433AB34E.90509@users.sourceforge.net> (raw)
Hey!
If you noted my last message and thougt that it was very noob, don't
count on any more advancement here. ;-)
The thing is that I need help to get started. I'm in the process of
learning C and I need to know how the kernel patching and distribution
works.
1 - I've looked into the kernel-janitor TODO list and I don't exactly
understand lines like this:
/Audit return codes (and handle failure correctly) for: /(What does
this mean???)/
- request_region() /(This one was tricky)/
/Where do I have to look for the code? Do I have to go to the _entire_
kernel tree?
2 - How do I start writing patches? This doesn't tell me much:
/Before attacking any of these, we suggest sending a few patches in
advance to see if you are doing something wrong, or if someone else
is already doing same work.
Read related threads in the mailing list archive.
/Which patches? Where do I find a TODO list of patches that need to be
done? The lkml mailing list don't say me much.
I hope this wasn't _too_ noob :-)
Dinolinux
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next reply other threads:[~2005-09-28 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 15:14 Dinolinux [this message]
2005-09-28 17:46 ` [KJ] Need to get some very basic things sorted out lounprime
2005-09-28 17:56 ` Alexey Dobriyan
2005-09-28 17:56 ` Randy.Dunlap
2005-09-28 18:20 ` Ricardo Nabinger Sanchez
2005-09-28 18:42 ` Randy.Dunlap
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=433AB34E.90509@users.sourceforge.net \
--to=slackfan@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.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.