From: Rishi Bhushan Agrawal <postrishi@gmail.com>
To: kernelnewbies@kernelnewbies.org
Cc: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"m vivek" <bitu.kv@gmail.com>
Subject: Re: Need help to get started
Date: Mon, 2 Mar 2020 12:55:11 +0530 [thread overview]
Message-ID: <CAEF38FH8Lqz2RHKtg8SMB45vaoho_gNnUGSbQQwnU6U_kd+_HQ@mail.gmail.com> (raw)
In-Reply-To: <403385.1582615591@turing-police>
[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]
On Tue, Feb 25, 2020 at 12:57 PM Valdis Klētnieks <valdis.kletnieks@vt.edu>
wrote:
> On Tue, 25 Feb 2020 12:08:53 +0530, m vivek said:
>
> > I just joined the mailing list. Excited to contribute to linux kernel but
> > finding it difficult to figure out where to start.
> >
> > Any help would be appreciated.
>
> Pretty much anything under drivers/staging is fair game - it's *all* code
> that needs fixing (if it didn't need fixing to be up to most kernel
> standards,
> it wouldn't be in drivers/staging :)
>
> Also, you probably want to go read this:
>
>
> https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
See if this helps https://lkw.readthedocs.io/en/latest/
--
Regards,
Rishi B. Agrawal
[-- Attachment #1.2: Type: text/html, Size: 1746 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-03-02 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 6:38 Need help to get started m vivek
2020-02-25 7:10 ` Greg KH
2020-02-25 7:26 ` Valdis Klētnieks
2020-03-02 7:25 ` Rishi Bhushan Agrawal [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=CAEF38FH8Lqz2RHKtg8SMB45vaoho_gNnUGSbQQwnU6U_kd+_HQ@mail.gmail.com \
--to=postrishi@gmail.com \
--cc=bitu.kv@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).