From: Aditya <yashsri421@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
dwaipayanray1@gmail.com
Subject: Re: [PATCH v3] checkpatch: fix false positives in REPEATED_WORD warning
Date: Sun, 25 Oct 2020 15:31:06 +0530 [thread overview]
Message-ID: <091ba604-d5a3-fe13-f13b-6b7e31ec63f6@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2010250627370.6697@felia>
On 25/10/20 11:21 am, Lukas Bulwahn wrote:
> This is a nice idea as well. And I recommend to do this kind of research
> looking at checkpatch and clang-format; both will not be the 'final tools'
> but I think if you can identify a good mix and combination of those two
> tools, we will get a good step forward of documenting the
> commonalities and differences of coding styles in the different
> subcommunities (the preferences of specific maintainers and subsystems).
>
> A last nice idea to consider:
>
> I would like to have an interactive checkpatch.pl mode where an authors
> can say that they ran checkpatch.pl, seen the warning and errors
> reported, but disagree and comment why they disagree. Then this kind of
> information is added to the patch in a non-disturbing area of the patch
> and we can pick up and aggregate that information from the patches to see
> the complaints, false positives to address or suggestions which rules
> should be disabled for some subcommunities.
>
> Aditya, your task is now to make those ideas more specific and write down
> a one to two page project proposal for the mentorship. It can be to some
> extent in bullet points as long as it is roughly understandable to all of
> us what you plan and would like to do.
>
> With that proposal accepted, you have shown to be applicable to the
> mentorship program here and we take care of the last organisational points
> before the start.
>
> Lukas
>
Alright Sir. I'll be sending my proposal in few days time, on the
basis of my formulated ideas.
Will let you know if I face any doubts during the procedure :)
Thanks
Aditya
prev parent reply other threads:[~2020-10-25 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 13:38 Aditya Srivastava
2020-10-23 19:06 ` Lukas Bulwahn
2020-10-23 20:19 ` Joe Perches
2020-10-24 13:24 ` Aditya
2020-10-24 15:33 ` Joe Perches
2020-10-24 18:12 ` Aditya
2020-10-25 5:51 ` Lukas Bulwahn
2020-10-25 6:06 ` Joe Perches
2020-10-25 6:11 ` Lukas Bulwahn
2020-10-25 10:01 ` Aditya [this message]
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=091ba604-d5a3-fe13-f13b-6b7e31ec63f6@gmail.com \
--to=yashsri421@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®