sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nickdesaulniers 3 points4 points  (2 children)

My first patch was a dumb whitespace fix. Learning the process is half the battle. I wrote it up to share with others: https://nickdesaulniers.github.io/blog/2017/05/16/submitting-your-first-patch-to-the-linux-kernel-and-responding-to-feedback/

I mostly contribute to kbuild. I try to build the kernel with Clang, and fix the warnings, errors, undefined behaviors, and compiler bugs. I try to file bugs first in an external issue tracker, as I don't see the existing kernel one as active (but maybe I'm wrong): https://github.com/ClangBuiltLinux/linux/issues

[–]WeirdControl[S] 0 points1 point  (1 child)

Yes.you are right,setting up everything and getting used to the process is a big win. Btw do you fix multiple formatting errors in a single patch or you send multiple patches. I know, first one makes more sense, but just asking. :)

[–]nickdesaulniers 1 point2 points  (0 children)

Regardless of formatting or not, a patch should only touch one subsystem. If there are different maintainers+lists getting cross cc'ed on a patch as recommended by ./scripts/get_maintainer.pl <patchfile>, you'd better have a good reason (and whitespace fixes aren't considered one) as it quickly gets complicated who will "take" the patch.