From: Rohit Sarkar <rohitsarkar5398@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kernel-janitors@vger.kernel.org, kernelnewbies@kernelnewbies.org
Subject: Re: Queries of an aspiring kernel developer
Date: Fri, 13 Sep 2019 19:49:35 +0530 [thread overview]
Message-ID: <20190913141935.GA309@SARKAR> (raw)
In-Reply-To: <20190913132310.GQ20699@kadam>
On Fri, Sep 13, 2019 at 04:23:10PM +0300, Dan Carpenter wrote:
> On Thu, Sep 12, 2019 at 07:55:17PM +0530, Rohit Sarkar wrote:
> > Hi Dan,
> > First things first, I know that sending private emails is frowned upon
> > but I was unsure if this would belong in the list.
>
> This does belong on the list. Especially the kernel-janitor list.
Added kernel-janitors and kernel-newbies to the thread.
> > Secondly I will keep
> > this as short as possible. (I know you are lazy :) )
> >
> > I have been interested in kernel development for a long time and want to
> > contribute to the community while learning and having fun.
> > Till now I have sent some minor patches:
> > [1]: Fixes typo
> > [2]: Checkpatch fix
> > [3]: Replaces snprintf with scnprintf
> >
> > I now would like to work on something that is not too trivial (like a
> > typo/checkpatch fix) and not too complex. I am finding it difficult to
> > come up with something substantial to work on.
>
> The various intern project probably have ideas. Julia Lawall may know.
>
Sure, will get in touch with her.
> > It would really help me if you could point me in a direction where I could
> > focus my efforts on.
>
> What I always tell people is to pick a small driver from staging. The
> iio drivers are pretty small. Just try to fix it as much as possible.
> Read it and re-read it and patch it and patch it. As you go you will
> learn more until you are the expert of that driver. Try to get it
> moved out of staging.
This sounds nice. Would this require any external hardware for testing?
> regards,
> dan carpenter
Thanks a lot for taking the time to reply.
Regards,
Rohit Sarkar
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next parent reply other threads:[~2019-09-16 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190912142517.GA22751@SARKAR>
[not found] ` <20190913132310.GQ20699@kadam>
2019-09-13 14:19 ` Rohit Sarkar [this message]
2019-09-13 14:24 ` Queries of an aspiring kernel developer Julia Lawall
2019-09-13 14:29 ` Rohit Sarkar
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=20190913141935.GA309@SARKAR \
--to=rohitsarkar5398@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).