archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <>
To: Shubham Gupta <>
Subject: Re: [Linux-kernel-mentees] Information regarding Linux Kernel: Evaluate and Improve
Date: Mon, 17 Aug 2020 11:46:05 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2008171144330.8645@felia> (raw)
In-Reply-To: <>

Dear Shubham,

The zeroth task is to learn suitable netiquette for the communication with 
the kernel community.

First, please do not top-post.

    A: Because we read from top to bottom, left to right.
    Q: Why should I start my reply below the quoted text?

    A: Because it messes up the order in which people normally read text.
    Q: Why is top-posting such a bad thing?

    A: The lost context.
    Q: What makes top-posted replies harder to read than bottom-posted?

    A: Yes.
    Q: Should I trim down the quoted part of an email to which I'm 

Second, please always CC:

Third, set up your email client according to the kernel community rules.

Then, the first task is to run on a few kernel patches and
collect the results. When you have that, please share your script with
me, e.g., in a github repository.

Hints to the first task:

Can you create a list of all non-merge commits that were added in the
version v5.8 of the kernel, i.e., all non-merge commits that are in v5.8
and not already in v5.7?

Can you share the script/command you executed and the resulting list on 

Can you run your script on all commits of this list above and record
all reports, and store them in your github repository?

Can you suggest ideas how to aggregate the findings and create a
statistics? For example: Which type of error is reported most?
Can you implement that idea?

I also suggest to have a look at
the options ./scripts/ --list-types and
./scripts/ --show-types. The option --show-types changes
the output of to list type identifiers, so it is easier
to parse and aggregate the output.

Please also share the script you create for that purpose on your
github repository.

The second task is to pick one warning that appears often and improve to handle that better and get it accepted by the kernel

Hints to the second task follow when the first task is solved.

If you fail on any of those tasks, you are out of the selection process.

Linux-kernel-mentees mailing list

           reply	other threads:[~2020-08-17  9:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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=alpine.DEB.2.21.2008171144330.8645@felia \ \ \ \

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