linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Ayush <ayush@disroot.org>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH v2] checkpatch: handle line break between commit and hash value
Date: Sun, 13 Sep 2020 13:01:33 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2009131220070.22585@felia> (raw)
In-Reply-To: <2f6509d8dfcf8eb7322771aec1817104@disroot.org>



On Sat, 12 Sep 2020, Ayush wrote:

> September 12, 2020 9:09 PM, "Ayush" <ayush@disroot.org> wrote:
> 
> > I am re-evaluating my output and will give you a analysis of all commits
> > which are getting affected by my patch.
> > It will take time to run checkpatch.pl again on those commits, so I will
> > share as soon as it's finished.
> 
> I fixed my script used for analysis and re-evaluated the affect of my patch.
> 
> I have made a list of commits which are fixed with this patch, It can be found here:
> 
> https://gist.githubusercontent.com/eldraco19/e7bf729b04cf6e2eee6ec52785b318d4/raw/74e13760fe01deee3285a1ec047ea0ac036cae76/commit_report.txt
> 
>

Did checkpatch.pl output on other types change?

One of the testers on this list reported that two COMMIT_LOG_LONG_LINE 
reports disappeared. That should not have happened, right?

I had a look at the checkpatch.pl output for commit 0a2bd55c194a ("dm 
integrity: document allow_discard option").

I think the reported line is wrong here.

Also, the line number for other cases have changed.

Generally, the line number should point to the line where the error really 
happens.

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

  reply	other threads:[~2020-09-13 11:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12  9:48 Ayush
2020-09-12 11:17 ` Lukas Bulwahn
2020-09-12 12:42 ` Lukas Bulwahn
2020-09-12 13:34 ` Ayush
2020-09-12 14:15 ` Lukas Bulwahn
2020-09-12 15:38 ` Ayush
2020-09-12 19:37 ` Ayush
2020-09-13 11:01   ` Lukas Bulwahn [this message]
2020-09-13 12:06   ` Ayush
2020-09-13 18:09     ` Lukas Bulwahn
2020-09-13 20:53     ` Ayush
2020-09-14  5:12       ` Lukas Bulwahn
2020-09-17 14:53       ` Ayush
2020-09-17 15:17         ` 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=alpine.DEB.2.21.2009131220070.22585@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=ayush@disroot.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --subject='Re: [Linux-kernel-mentees] [PATCH v2] checkpatch: handle line break between commit and hash value' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox