From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Ujjwal Kumar <ujjwalkumar0501@gmail.com>, Ayush <ayush@disroot.org>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: [Linux-kernel-mentees] RRRe: Evaluate and Improve checkpatch: tasks
Date: Wed, 16 Sep 2020 14:06:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2009161352170.12662@felia> (raw)
In-Reply-To: <e6fa87d7-3b80-390f-4db2-40e977a4b635@gmail.com>
On Wed, 16 Sep 2020, Ujjwal Kumar wrote:
> On 13/09/20 4:45 pm, Lukas Bulwahn wrote:
> >
> >
> > On Sun, 13 Sep 2020, Ujjwal Kumar wrote:
> >
> >> On 12/09/20 6:02 pm, Lukas Bulwahn wrote:
> >>> On Sat, 12 Sep 2020, Ujjwal Kumar wrote:
> >>>
> >>>> On 12/09/20 5:14 pm, Lukas Bulwahn wrote:
> >>>>>
> >>>>>
> >>>>> On Sat, 12 Sep 2020, Ujjwal Kumar wrote:
> >>>>>
> >>>>>> Hello Lukas,
> >>>>>>
> >>>>>> I attempted the tasks.
> >>>>>>
> >>>>>> Below is the link of GitHub repository containing my write-up and findings.
> >>>>>> https://github.com/Ujjwal0501/lkmp-checkpatch
> >>>>>>
> >>>>>
> >>>>> Thanks, it shows 404. Good luck next time.
> >>>>
> >>>> I'm really sorry for the noise. The link is active now.
> >>>
> >>> Okay, scripts and data looks sound. So, let us try those scripts.
> >>>
> >>> Please have a look at this patch:
> >>>
> >>> https://lore.kernel.org/linux-kernel-mentees/20200912094826.150170-1-ayush@disroot.org/
> >>>
> >>> The author states:
> >>>
> >>> This issue was discovered through a thorough analysis of checkpatch.pl
> >>> errors and warnings of type GIT_COMMIT_ID on commits between v5.7 and
> >>> v5.8.
> >>>
> >>> Before applying this patch, checkpatch.pl reported 342 errors of type
> >>> GIT_COMMIT_ID. After applying patch, errors reduced to 284.
> >>>
> >>>
> >>> If your scripts work, you should be able to confirm the statement.
> >>>
> >>
> >> I'm unable to reproduce the same count as above because the script is run
> >> on different sets of commits.
> >>
> >
> > So, you say the evaluation from Ayush was not really a good evaluation of
> > v5.7..v.5.8 due to some misconception of Ayush how to obtain the set of
> > proper commits from v5.7..v5.8?
>
> That is not totally correct as he correctly generated the list of commits in
> the first task. But the script used to generate the statistics used a
> different way so I was trying to point that specific thing.
>
> >>
> >>> The tasks are:
> >>>
> >>> 1. Run your scripts and create a full statistics of all error types with
> >>> their according count for v5.7..v5.8.
> >>>
> >>> 2. Apply the patch with git am.
> >>>
> >>> 3. Run your scripts again and create a new statistics.
> >>>
> >>> 4. Compare before and after
> >>>
> >>> 5. Make all results available on your github repository.
> >>>
> >>
> >> The results are available at the link
> >> https://github.com/Ujjwal0501/lkmp-checkpatch/blob/master/tasks.md
> >>
> >> Kindly take a look at it.
> >>
> >
> > Can you share the errors that have changed after the patch was applied?
> >
> > - Which cases of GIT_COMMIT_ID have disappeared?
> > - Which cases of GIT_COMMIT_ID are new?
> > - Which cases of GIT_COMMIT_ID have changed?
> > - Have cases of other type of errors/warnings/checks/notes disappeared,
> > been added or changed?
> >
> > You state GIT_COMMIT_ID changed from 272 to 230, but the tester in
> >
> > https://lore.kernel.org/linux-kernel-mentees/CABJPP5BFNjBhdcvBWqDYnR-o2sZ0oY77bYr9PxducXW4Y=482Q@mail.gmail.com/
> >
> > claimed that it changed from 270 to 251.
> >
> > Which numbers are right? Why is there a difference in both statistics?
>
> The patch from Ayush appears to have a bug which I have detailed in my write up.
>
> Kindly take a look at the link.
> https://github.com/Ujjwal0501/lkmp-checkpatch/blob/master/followuptask1.md
>
Ayush, please fix the bug.
Ujjwal, please do not create screenshots. That is wasteful and harmful to
the environment.
You can share the same information by sharing plain text in nicely
formated ways.
Ujjwal, I do not understand the diff you presented. We are really not
acquainted with your stat file, maybe you can explain what you read out of
that.
Which results are from which exact commit?
Ujjwal, can you judge if the findings that disappeared should have not
been warned about in the first place?
And the ones that appear new? Should they be really warned about or not?
Are there further patterns in the GIT_COMMIT_ID findings that probably
should not be warned about and could be improved?
Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2020-09-16 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 11:38 [Linux-kernel-mentees] Evaluate and Improve checkpatch: tasks Ujjwal Kumar
2020-09-12 11:44 ` Lukas Bulwahn
2020-09-12 11:48 ` Ujjwal Kumar
2020-09-12 12:32 ` Lukas Bulwahn
2020-09-13 9:35 ` Ujjwal Kumar
2020-09-13 11:15 ` Lukas Bulwahn
2020-09-16 11:36 ` Ujjwal Kumar
2020-09-16 12:06 ` Lukas Bulwahn [this message]
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=alpine.DEB.2.21.2009161352170.12662@felia \
--to=lukas.bulwahn@gmail.com \
--cc=ayush@disroot.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=ujjwalkumar0501@gmail.com \
/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).