linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: ANUSHREE SABNIS <absabnis_b19@me.vjti.ac.in>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: Linux Kernel: Checkpatch Documentation
Date: Sun, 22 Aug 2021 23:51:04 +0530	[thread overview]
Message-ID: <CABJPP5AUxhvn=r9fW5xc5Ux2+Ya8dR=P6_JjG-xU8x3RJFesJQ@mail.gmail.com> (raw)
In-Reply-To: <CAE3uYxtgef1YPKsWBqt232f62y14gtFvy1S-mTZ2woU+uR5TzA@mail.gmail.com>

On Thu, Aug 12, 2021 at 9:04 PM ANUSHREE SABNIS
<absabnis_b19@me.vjti.ac.in> wrote:
>
> Respected mentors,   I am interested in the Checkpatch Documentation mentorship program and I would like to work on the tasks for the mentee selection.
> Sincerely,
> Anushree Sabnis

Thanks for your interest in working with the checkpatch documentation.

The zeroth task is to learn suitable netiquette for the communication with
the kernel community. Below are some basic rules and pointers for this
mentorship. More information on kernel netiquette is also at
https://people.kernel.org/tglx/notes-about-netiquette.

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 replying?

Second, please always CC: linux-kernel-mentees@lists.linuxfoundation.org.

Third, set up your email client according to the kernel community
rules. Here is some information to that:

https://www.kernel.org/doc/html/latest/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
https://www.kernel.org/doc/html/latest/process/email-clients.html

Generally more information on submitting patches and responding on
replies is at https://www.kernel.org/doc/html/latest/process/submitting-patches.html

Once the zeroth task is understood, you can now move on to the first
task: Running checkpatch on a specific file.

Get a clone of the Linux kernel repository.
The script checkpatch.pl is under the scripts directory.

Then, the first task is to run checkpatch.pl on a few files below
and share the results:

drivers/dma/qcom/gpi.c
drivers/pinctrl/berlin/berlin.c

Which information on these rules that checkpatch warns about
is available in the Checkpatch Documentation?

If documentation of these rules is available, explain your
understanding of the rules in your own words.
If no information is available in the documentation,
explain your understanding of the rule.

In any case, explain the violation that is checked and raised in the
checkpatch script, i.e., what is implemented in checkpatch to check
the rule and possible violations. Which code in the checkpatch script
is raising the warning? What does it check and how is that
implemented?

Explain how to possibly fix this code with regards to that violation.

Once you succeed on this first task, we inform you about the further
second and third task. If you fail on any of those tasks, you are out
of the selection process.

The selection of the mentee will happen according to schedule,
at earliest on August 12th and at latest at the end of August.
More information is available at
https://docs.linuxfoundation.org/lfx/mentorship/mentorship-program-timelines.

All the best,
Dwaipayan.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2021-08-22 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 15:34 Linux Kernel: Checkpatch Documentation ANUSHREE SABNIS
2021-08-22 18:21 ` Dwaipayan Ray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-01  8:13 Anuj Pandey
2021-08-01 21:16 ` Dwaipayan Ray
2021-07-20  5:37 Ameya Deshpande
2021-07-20  5:58 ` Dwaipayan Ray

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='CABJPP5AUxhvn=r9fW5xc5Ux2+Ya8dR=P6_JjG-xU8x3RJFesJQ@mail.gmail.com' \
    --to=dwaipayanray1@gmail.com \
    --cc=absabnis_b19@me.vjti.ac.in \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    /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).