From: sharma.kernel@gmail.com (Abhishek)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Request for guidance
Date: Tue, 24 May 2016 20:22:15 +0530 [thread overview]
Message-ID: <57446A9F.7090605@gmail.com> (raw)
In-Reply-To: <CAGUYZuTmfTbcNq-rN6dxL4nEbKTOsP6O8iVjp8wLO8T5-_s1Vw@mail.gmail.com>
On Tuesday 24 May 2016 10:17 AM, sanjeev sharma wrote:
> Hi Abhishek,
>
> There are some open source project where you can contribute too but I
> would suggest first you to work on Kernel Bugs available at
> https://bugzilla.kernel.org. This would boost your confidence.
Thanks Sanjeev.
Is there anything else that I can do in parallel with bugzilla?
>
> Regards
> Sanjeev Sharma
>
>
>
> On Tue, May 24, 2016 at 7:06 AM, Abhishek <sharma.kernel@gmail.com
> <mailto:sharma.kernel@gmail.com>> wrote:
>
> Hi All,
>
> I am an Embedded Software Engineer with 3+ years of experience. I am
> fascinated by kernel development and want to be a device driver
> developer.
>
> I have done following so far.
> #Studied LDD3.
> #Subscribed to eudyptula challenge and submitted solution
> for 4th task(waiting for next task).
> #Have compiled and installed kernel successfully on multiple boards.
>
> I want to start contributing to kernel so I looked into staging and
> found that I can not work on TODO unless I have required hardware to
> test patch (which unfortunately I don't have).
>
> Requesting you to guide me about how to start working on
> kernel/device drivers development.
>
> Thanks,
> Abhishek
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> <mailto:Kernelnewbies@kernelnewbies.org>
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
next prev parent reply other threads:[~2016-05-24 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 1:36 Request for guidance Abhishek
2016-05-24 4:47 ` sanjeev sharma
2016-05-24 14:52 ` Abhishek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-20 1:19 Abhishek
2016-05-29 19:19 ` Manavendra Nath Manav
2016-06-01 7:27 ` Drew Fustini
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=57446A9F.7090605@gmail.com \
--to=sharma.kernel@gmail.com \
--cc=kernelnewbies@lists.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).