<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 9, 2020, 3:19 PM Lukas Bulwahn <<a href="mailto:lukas.bulwahn@gmail.com">lukas.bulwahn@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On Wed, 9 Sep 2020, Alaa Emad wrote:<br>
<br>
> Hello Lukas Bulwahn,<br>
> i hope this email finds you well , i applied for Linux Kernel: Evaluate and Improve <a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a><br>
> <br>
> according to the first two tasks, i am unemployed how should i respond to these?<br>
><br>
<br>
I do not know which list of tasks you are referring to. So, I cannot <br>
comment on the first two tasks.<br></blockquote></div></div><div dir="auto"> </div><div dir="auto"> 1.Participation permission from school or employer.</div><div dir="auto"> 2.School Enrollment Verification.</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> also are there any resources to run and patch the <a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> , Please? <br>
><br>
<br>
Here is some starting information:<br>
<br>
The zeroth task is to learn suitable netiquette for the communication with <br>
the kernel community.<br>
<br>
First, please do not top-post.<br>
<br>
A: Because we read from top to bottom, left to right.<br>
Q: Why should I start my reply below the quoted text?<br>
<br>
A: Because it messes up the order in which people normally read text.<br>
Q: Why is top-posting such a bad thing?<br>
<br>
A: The lost context.<br>
Q: What makes top-posted replies harder to read than bottom-posted?<br>
<br>
A: Yes.<br>
Q: Should I trim down the quoted part of an email to which I'm <br>
replying?<br><br>I understood. <br></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Second, please always CC: <a href="mailto:linux-kernel-mentees@lists.linuxfoundation.org" target="_blank" rel="noreferrer">linux-kernel-mentees@lists.linuxfoundation.org</a>.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto"> done</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Third, set up your email client according to the kernel community rules.<br>
<br>
<br>
<br>
Then, the first task is to run <a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> on a few kernel patches and<br>
collect the results. When you have that, please share your script with<br>
me, e.g., in a github repository.<br>
<br>
<br>
Hints to the first task:<br>
<br>
Can you create a list of all non-merge commits that were added in the<br>
version v5.8 of the kernel, i.e., all non-merge commits that are in v5.8<br>
and not already in v5.7?<br>
<br>
Can you share the script/command you executed and the resulting list on <br>
github?<br>
<br>
Can you run your script on all commits of this list above and record<br>
all <a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> reports, and store them in your github repository?<br>
<br>
Can you suggest ideas how to aggregate the findings and create a<br>
statistics? For example: Which type of error is reported most?<br>
Can you implement that idea?<br>
<br>
<br>
I also suggest to have a look at<br>
the options ./scripts/<a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> --list-types and<br>
./scripts/<a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> --show-types. The option --show-types changes<br>
the output of <a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> to list type identifiers, so it is easier<br>
to parse and aggregate the output.<br>
<br>
Please also share the script you create for that purpose on your<br>
github repository.<br>
<br>
<br>
<br>
The second task is to pick one warning that appears often and improve<br>
<a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a> to handle that better and get it accepted by the kernel<br>
community.<br>
<br>
Hints to the second task follow when the first task is solved.<br>
<br>
If you fail on any of those tasks, you are out of the selection process.<br>
<br>
I could implement that with just a few lines of code changes, but please <br>
do not underestimate the learning curve here. I hope you are very fit in <br>
Perl, that is required for this project.<br>
<br>
The selection of the mentee will happen at the end of this month.<br>
<br>
So, the first task should be done within this first week, so that you<br>
have time for changing <a href="http://checkpatch.pl" rel="noreferrer noreferrer" target="_blank">checkpatch.pl</a>, testing and discussing the<br>
change<br><br><br>Thank you for your hints, i will do check these points and return back to you </blockquote></div></div><div dir="auto"> </div><div dir="auto"> Alaa</div><div dir="auto"><br></div><div dir="auto"></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Lukas<br>
<br>
> Thanks in advance ,<br>
> Alaa Emad<br>
> <br>
> </blockquote></div></div></div>