archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <>
To: Aditya Srivastava <>
Subject: Re: [Linux-kernel-mentees] tasks for Community Bridge Program
Date: Mon, 12 Oct 2020 14:57:33 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Oct 12, 2020 at 11:38 AM Aditya Srivastava <> wrote:
> 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:

Your email client is broken; you cannot send emails to a kernel
mailing list with this email setup. I will not bother to use a proper
email client either :)

summary at

looks good.

Dwaipayan probably needs to look into the details here.

E.g., why did those really unrelated issues change?

AVOID_BUG 240 239

Let us see if we can make sense of this evaluation.

Linux-kernel-mentees mailing list

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12  9:38 [Linux-kernel-mentees] tasks for Community Bridge Program Aditya Srivastava
2020-10-12 12:57 ` Lukas Bulwahn [this message]
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 \ \ \ \ \

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