some advices

some advices

[Adir Kuhn]

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?

Regards,
--
Adir Kuhn

Re: some advices

[Julia Lawall]

On Tue, 5 May 2015, 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?

It's probably best to avoid changes that affect only whitespace.  Changes 
that make the code more readable, or use more modern APIs may be more 
successful.  If you want to start with whitespace changes, try staging 
code.

julia


> 
> Regards,
> --
> Adir Kuhn
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: some advices

[Dan Carpenter]

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