Re: Kernel first task

Re: Kernel first task

[Cláudio Maia]

On 10/07/21 12:22, Anton Baltser wrote:
> Hello,
>
> I'm trying to get involved into Kernel Devolopment and confused about where I can take the first task to complete. AFAIK this is usually a code cleanup task, but what kind of code cleanup is available to do.
>
> Thanks!
>
> Regards,
> Anton Baltser.

For an easy to follow introduction on how to submit your first patch, you can watch this talk (https://www.youtube.com/watch?v=LLBrBBImJt4) by Greg Kroah-Hartman at FOSDEM 2010 entitled "Write and Submit your first Linux kernel Patch". I believe this is a good starting point to guide through the process.

Regards,
Cláudio Maia

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Kernel first task

[Greg KH]

On Sat, Jul 10, 2021 at 11:22:59AM +0000, Anton Baltser wrote:
> Hello,
> I'm trying to get involved into Kernel Devolopment and confused about
> where I can take the first task to complete. AFAIK this is usually a
> code cleanup task, but what kind of code cleanup is available to do.

Look at drivers/staging/*/TODO for items to start out with.

Have fun!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Kernel first task

[Valdis Klētnieks]

[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]

On Sat, 10 Jul 2021 11:22:59 -0000, Anton Baltser said:

> I'm trying to get involved into Kernel Devolopment and confused about where I
> can take the first task to complete.

There's always low-hanging fruit in drivers/staging.  The various drivers there
*should* have a TODO.  And of course pretty much everything in drivers/staging
needs typo fixes and fixing formatting, so those are always easy targets - just
don't blindly fix checkpatch.pl warnings without checking that the fix actually
makes the code better - there's been plenty of submitted patches for "goes past
column 80" that just made things uglier.

If you're feeling more ambitious, go through the TODOs - and clean out
entries that have already been taken care of. This might not be a good
thing for a first-time kernel hacker, as you'll need some experience with
git to really sort out what's been done.

You should also go read this:
https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html
and then ask yourself *why* you're wanting to submit patches.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies