<br><br>On Monday, January 26, 2015, Robert P. J. Day <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 26 Jan 2015, Jeshwanth Kumar N K wrote:<br>
<br>
> Hi Satwanjit,<br>
><br>
> If you are doing for final year project, my suggestion is develop<br>
> some userspace tools which is not available and useful one. Probably<br>
> getting info from kernel and display some info etc. Right now I am<br>
> not getting any idea, but developing a tool is good idea. U can<br>
> identify.<br>
><br>
> I am mentioning above one because by haven't mentioned any kernel<br>
> topics u know.<br>
<br>
what's wrong with ftrace? but seriously, you know what newcomers<br>
might get some value out of doing if they want to contribute? writing<br>
some really, really good documentation or tutorials.<br>
<br>
the mainline kernel developers are, unsurprisingly, tres busy doing,<br>
you know, developing, and often the code gets ahead of the docs. so if<br>
you want, pick a subsystem, read up on it and see if it needs improved<br>
documentation. then write it. there are lots of benefits to this.<br>
<br>
first, there is *always* a desperate need for better documentation,<br>
and absolutely *no* *one* will discourage you from writing docs.<br>
<br>
second, you can't really f**k things up if you stick to<br>
documentation, and because it represents non-functional changes,<br>
you're way more likely to get your patches applied than if you were<br>
trying to contribute code.<br>
<br>
and third (without naming names), if you just want to start getting<br>
your name into the kernel git log (and there's nothing wrong with<br>
having that ambition since it's something you can brag about), it<br>
doesn't get much easier than updating the in-kernel docs.<br>
<br>
if you want a specific project, here's one. start combing through<br>
the Documentation/ directory and identifying the stuff that is<br>
craptastically out of date. there's a lot of docs there, and piles of<br>
it is suffering from neglect. some of it could stand to be updated,<br>
while some of it could stand to be deleted entirely.<br>
<br>
so start reading, and comparing that documentation to the current<br>
kernel source, and start submitting changes to update it. there ... is<br>
that specific enough of a suggestion?<br>
<br>
rday<br>
<br>
--<br>
<br></blockquote><div><br></div><div>Robert, Documentation is really good idea :). </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
========================================================================<br>
Robert P. J. Day Ottawa, Ontario, CANADA<br>
<a href="http://crashcourse.ca" target="_blank">http://crashcourse.ca</a><br>
<br>
Twitter: <a href="http://twitter.com/rpjday" target="_blank">http://twitter.com/rpjday</a><br>
LinkedIn: <a href="http://ca.linkedin.com/in/rpjday" target="_blank">http://ca.linkedin.com/in/rpjday</a><br>
========================================================================<br>
<br>
</blockquote><br><br>-- <br><div dir="ltr"><div>Regards<br>Jeshwanth Kumar N K<br></div>Bangalore, India<br></div><br>