From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: some advices
Date: Tue, 05 May 2015 09:01:26 +0000 [thread overview]
Message-ID: <20150505090126.GS14154@mwanda> (raw)
In-Reply-To: <CAPmfwEkA6GZLtmNHno3OYOG31cbDx_5kZpqho4f+KEb75XKGzg@mail.gmail.com>
On Tue, May 05, 2015 at 12:21:53AM -0300, Adir Kuhn wrote:
> Hi everybody, I'm quite new here and I want to be a kernel developer
> so where I can start? I dowloaded the linux kernel source and followed
> the tips for the first patch on the kernelnewbies but sometimes these
> patches are not acepted because is too simple (just cleaning code
> style). So there is something else that I can study or some trivial
> bug to fix to feel me more confident on linux development?
>
If you send code style changes to staging they will accept anything.
But if you want to learn then stay on the same driver and just focus on
sending patches for it until you understand it completely.
You could also fix GCC warnings, cppcheck, or clang stuff.
regards,
dan carpentr
prev parent reply other threads:[~2015-05-05 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 3:21 some advices Adir Kuhn
2015-05-05 5:13 ` Julia Lawall
2015-05-05 9:01 ` Dan Carpenter [this message]
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=20150505090126.GS14154@mwanda \
--to=dan.carpenter@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox