archive mirror
 help / color / mirror / Atom feed
From: Aditya Srivastava <>
Subject: [Linux-kernel-mentees] tasks for Community Bridge Program
Date: Mon, 12 Oct 2020 15:08:12 +0530	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1647 bytes --]

Dear Sir/Ma'am
I have performed some tasks on to find out the aggregate and
summary of Errors and Warnings that have been generated on certain Linux
Kernel Versions' commits . The summary of my tasks are as follows:
1. Task1: Create a list of all non-merge commits that were added in the
version v5.8 but were not there in v5.7. Run script on these
commits and create a statistical summary of findings.
My findings:
My Scripts for this task:

2. Task2: Test what are errors and warnings by reports on
v5.6..v5.8. Generate a report with respect to changes suggested by
Dwaipayan Ray (,
to present the differences in a suitable aggregated form, to find out the
kind of errors and warnings that are changing.

My Findings:
Change in the number of warnings and errors:

Individual summary report generated by
After the commit:

Before the commit:

Scripts used for this task:

Thanks and Regards

[-- Attachment #1.2: Type: text/html, Size: 2832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

Linux-kernel-mentees mailing list

             reply	other threads:[~2020-10-12  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12  9:38 Aditya Srivastava [this message]
2020-10-12 12:57 ` [Linux-kernel-mentees] tasks for Community Bridge Program Lukas Bulwahn
2020-10-12 18:23   ` Dwaipayan Ray
2020-10-12 18:28     ` Lukas Bulwahn
2020-10-12 21:11       ` Aditya Srivastava
2020-10-14  7:10         ` Aditya
2020-10-14  7:22           ` Lukas Bulwahn

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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).