<div dir="ltr"><span style="font-size:12.8px">Hi Ashijeet,</span><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Its almost always true that we all start off with bugzilla and i believe you should start from there as well. ( pick up bite size bugs) and start solving.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">However, there is another very important thing. C programming will help you code in a solution to the problem and often that's the most easiest part.</div><div style="font-size:12.8px">Its highly important that you understand the problem first. </div><div style="font-size:12.8px">Understand the subsystems , how they interact . I would urge you to first read about the linux kernel and how it explains all the subsystems and then start looking at the issues.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">You can solve small issues for the fun of it. But the real strength(at least if you ask me) of a kernel Engineer is to understand the problem first.</div><div style="font-size:12.8px">There are lots of materials online. But if you wish to read any specific book then <a href="https://books.google.co.in/books/about/Unix_Internals.html?id=Z7qfu9NK7WQC" target="_blank">https://books.google.co.in/books/about/Unix_Internals.html?id=Z7qfu9NK7WQC</a></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">That's where i started from</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 20, 2016 at 1:24 PM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, 20 Jul 2016, Aleksander Alekseev wrote:<br>
<br>
> Hello, Ashijeet<br>
><br>
> > I am kernel newbie and I was looking for something to work upon to<br>
> > improve my skill-set. I have good knowledge of C and experience in<br>
> > writing patches. Also please refer me if there is a to-do list for<br>
> > newbies related to pending tasks for linux kernel.<br>
><br>
> I'm newbie here as well. Still I have an experience of working on some<br>
> other open source projects. I believe the idea is always the same.<br>
><br>
> First, take a look on project's issue tracker:<br>
><br>
> <a href="https://bugzilla.kernel.org/" rel="noreferrer" target="_blank">https://bugzilla.kernel.org/</a><br>
><br>
> Also you could probably review an existing code and propose refactoring<br>
> or optimization patches. Static code analyzers is always a good start<br>
> point. Try looking for typos in comments - you will be surprised how<br>
> many mistakes are there. Usually people like to write code but don't<br>
> like to document and/or test it. Join testing and reviewing new<br>
> patches, try to improve them.<br>
><br>
> I hope this will help.<br>
<br>
</span> i've mentioned this before ... if you want a safe project that will<br>
still teach you a whole lot about the kernel, improve all the<br>
documentation under the Documentation/ directory. there's a *ton* of<br>
stuff there that is either in need of improving or, in some cases,<br>
deletion because it's so old. or if you're feeling really ambitious,<br>
write some *new* documentation for some subsystem for which there is<br>
none.<br>
<br>
and, finally, you can't screw things up by changing the docs.<br>
<br>
rday<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
<br>
========================================================================<br>
Robert P. J. Day Ottawa, Ontario, CANADA<br>
<a href="http://crashcourse.ca" rel="noreferrer" target="_blank">http://crashcourse.ca</a><br>
<br>
Twitter: <a href="http://twitter.com/rpjday" rel="noreferrer" target="_blank">http://twitter.com/rpjday</a><br>
LinkedIn: <a href="http://ca.linkedin.com/in/rpjday" rel="noreferrer" target="_blank">http://ca.linkedin.com/in/rpjday</a><br>
========================================================================<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</div></div></blockquote></div><br></div>