public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: kernelnewbies@kernelnewbies.org
Cc: Dhruva gole <goledhruva@gmail.com>
Subject: Re: First Time Contributor: Looking for Good Beginner issues
Date: Sun, 30 Jan 2022 16:48:34 +0100	[thread overview]
Message-ID: <3165559.44csPzL39Z@linux-zf1o> (raw)
In-Reply-To: <CALQfBwxNbZpA8Mt05_EEh+LoHhXggQfC2G8B+FCa4evUgkujxA@mail.gmail.com>

On sabato 22 gennaio 2022 08:13:53 CET Dhruva gole wrote:
> [...]
> 
> Kindly let me know where I can contribute as a beginner to the kernel.
> 
The best place to start hacking the Linux kernel is the drivers/staging subsystem.

Each subdirectory has its own TODO file which lists what the maintainers and
regular contributors expect it to be done to finally move a driver out from staging
to the more mature parts of the kernel.

For how to set up your development tools and to understand how to work
with the Linux kernel community, refer to kernelnewbies.org:

https://kernelnewbies.org/FirstKernelPatch

Regards,

Fabio M. De Francesco

P.S.: This question has been answered lots of times. Before asking, one should better
do some homework (Google search and the likes)  :) :) :)
 




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

      reply	other threads:[~2022-01-30 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  7:13 First Time Contributor: Looking for Good Beginner issues Dhruva gole
2022-01-30 15:48 ` Fabio M. De Francesco [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=3165559.44csPzL39Z@linux-zf1o \
    --to=fmdefrancesco@gmail.com \
    --cc=goledhruva@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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