linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Aditya <yashsri421@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] checkpatch: add fix for BAD_SIGN_OFF
Date: Sat, 7 Nov 2020 14:57:24 +0530	[thread overview]
Message-ID: <6fca02c0-4c4d-c6bd-67b2-35304cf25499@gmail.com> (raw)
In-Reply-To: <CAKXUXMzx=UacWsoPyiD5AVtfBpVDCcJpAFMo8OpXrf+KNpBFww@mail.gmail.com>

On 4/11/20 4:44 pm, Lukas Bulwahn wrote:
> On Tue, Nov 3, 2020 at 4:19 PM Aditya Srivastava <yashsri421@gmail.com> wrote:
>>
>> Currently, checkpatch warns us if the author of the commit signs-off
>> as co-developed-by.
>> E.g. for commit 6e88559470f5 ("Documentation: Add section about
>> CPU vulnerabilities for Spectre") we get:
>>
>> WARNING: Co-developed-by: should not be used to attribute nominal
>> patch author 'Tim Chen <tim.c.chen@linux.intel.com>'
>> Co-developed-by: Tim Chen <tim.c.chen@linux.intel.com>
>>
>> Provide a simple fix by removing the co-developed-by line from the
>> commit message
>>
> 
> Patch looks good. Maybe you can add a statistics on how many cases of
> the last 200,000 commits this rule would actually trigger?
> 
> E.g., you can probably quickly filter all commits that have at least
> one Co-developed-by tag among those last 200,000 commits (that is
> already only a few thousands), then take that list and just check with
> checkpatch.pl for this one rule quickly to see how often the rule
> would even trigger at all.
> 
> Once you have that and explain that in the commit message, I think the
> patch is ready for lkml and Joe Perches.
> 
> Lukas
> 

Hi Sir
I generated a report for around 200,000 commits (v4.13..v5.8), and
found that this rule was being triggered only 6 times. Statistically
this doesn't seem much. Is it still advisable to mention it in the
commit message?
Although, there's a possibility that user fixed this issue after
receiving the warning manually before committing.

Thanks
Aditya

_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2020-11-07  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 15:18 [Linux-kernel-mentees] [PATCH] checkpatch: add fix for BAD_SIGN_OFF Aditya Srivastava
2020-11-04 11:14 ` Lukas Bulwahn
2020-11-07  9:27   ` Aditya [this message]
2020-11-07 18:38     ` Lukas Bulwahn
2020-11-07 18:55       ` Aditya
2020-11-08  6:47         ` Lukas Bulwahn
2020-11-08  9:19           ` Aditya
2020-11-08 10:42             ` Lukas Bulwahn
2020-11-08 13:41 Aditya Srivastava
2020-11-08 13:43 Aditya Srivastava
2020-11-08 19:57 ` Joe Perches
2020-11-09  7:24   ` Aditya
2020-12-04 10:06   ` Aditya

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=6fca02c0-4c4d-c6bd-67b2-35304cf25499@gmail.com \
    --to=yashsri421@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).