From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Linux kernel checkpatch.pl mentorship
Date: Mon, 14 Sep 2020 00:09:11 +0530 [thread overview]
Message-ID: <CABJPP5BaUss9pWq=e+UDmVvr-puJsBtSVppST+CTcB8JkEdLmQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2009132010300.6806@felia>
[-- Attachment #1.1: Type: text/plain, Size: 847 bytes --]
> You should also try to find a case where checkpatch.pl can be improved:
>
> - It is best if you look at the checkpatch.pl error/warning reports and
> check if you can find a class of typical false positives in the reported
> data. Then, think about how to make the pattern in checkpatch and propose
> a patch to checkpatch.pl on this mailing list; with the evaluation data
> backing that your patch really improves the situation. We will then test
> and check your patch as well.
>
> - If you really cannot find a typical false positive, maybe you can take
> the task from Ayush to fix checkpatch with git ranges?
>
Hi,
I will try to find and evaluate the possiblity of such a case, and report
my finding
as soon as I find something substantial.
I may also require some advice from you on the patch submission process.
Thanking you,
Dwaipayan
[-- Attachment #1.2: Type: text/html, Size: 1174 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-09-13 18:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABJPP5CSa_QowD-O3_E5ndoQJvuBv=n2x5WG-acwQKE=rt5+Rw@mail.gmail.com>
[not found] ` <alpine.DEB.2.21.2009110925160.9220@felia>
2020-09-12 9:09 ` [Linux-kernel-mentees] Linux kernel checkpatch.pl mentorship Dwaipayan Ray
2020-09-12 11:03 ` Lukas Bulwahn
2020-09-12 12:08 ` Dwaipayan Ray
2020-09-12 12:21 ` Lukas Bulwahn
2020-09-13 8:16 ` Dwaipayan Ray
2020-09-13 11:05 ` Lukas Bulwahn
[not found] ` <CABJPP5BmRcC+OTSjuX_QrYononVq__DkhjGOgiKrP147MAXK+g@mail.gmail.com>
[not found] ` <alpine.DEB.2.21.2009132015570.6806@felia>
2020-09-13 18:23 ` Dwaipayan Ray
[not found] ` <alpine.DEB.2.21.2009132010300.6806@felia>
2020-09-13 18:39 ` Dwaipayan Ray [this message]
2020-09-14 5:17 ` Lukas Bulwahn
2020-09-14 12:31 ` Dwaipayan Ray
2020-09-14 13:49 ` Lukas Bulwahn
2020-09-14 15:39 ` Dwaipayan Ray
2020-09-14 18:32 ` Lukas Bulwahn
2020-09-15 13:04 ` Dwaipayan Ray
2020-09-16 7:01 ` Lukas Bulwahn
2020-09-17 13:09 ` Dwaipayan Ray
2020-09-17 13:41 ` Dwaipayan Ray
2020-09-17 14:18 ` Lukas Bulwahn
2020-09-17 14:43 ` Dwaipayan Ray
2020-09-17 15:03 ` Lukas Bulwahn
2020-09-17 14:13 ` 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:
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='CABJPP5BaUss9pWq=e+UDmVvr-puJsBtSVppST+CTcB8JkEdLmQ@mail.gmail.com' \
--to=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=lukas.bulwahn@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).