qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <cfontana@suse.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [RFC v3] checkpatch: detect missing changes to trace-events
Date: Mon, 14 Sep 2020 16:49:56 +0200	[thread overview]
Message-ID: <cf51a4d1-f760-dd83-fde8-9e9121daae50@suse.de> (raw)
In-Reply-To: <20200914134442.GN579094@stefanha-x1.localdomain>

On 9/14/20 3:44 PM, Stefan Hajnoczi wrote:
> On Tue, Aug 11, 2020 at 10:11:58AM +0200, Claudio Fontana wrote:
>> Signed-off-by: Claudio Fontana <cfontana@suse.de>
>> ---
>>  scripts/checkpatch.pl | 48 ++++++++++++++++++++++++++++++++++++------------
>>  1 file changed, 36 insertions(+), 12 deletions(-)
>>
>> v2 -> v3 :
>>
>> * move the check for missing changes to MAINTAINERS and trace-events
>>   later on, as otherwise the check for in_commit_log will not be done
>>   on an up to date value, causing fromfile and realfile to not be set,
>>   and matching unwanted strings inside the commit log.
>>
>> * Ensure that at least one file name is passed to grep.
>>
>>
>> ----
>>
>> v1 -> v2 :
>>
>> * track the "from" file in addition to the "to" file,
>>   and grep into both (if they exist), looking for trace.h, trace-root.h
>>
>>   If files are reachable and readable, emit a warning if there is no
>>   update to trace-events.
> 
> This patch still has an RFC tag. Is it ready to be merged?
> 
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> 

Hi Stefan, I think it's actually not, I would like to have more testing on it, checking all false positive/false negative cases.
I found some issues with it, with false negatives, that I still do not understand.

If anybody wants to rework this taking this as starting point, that's good, otherwise I will get back to it when I can..

I am not sure about the "move the check" part in v2 -> v3, and if anybody has more input and can help to understand this aspect, welcome to collaborate on this.

Ciao,

CLaudio


      reply	other threads:[~2020-09-14 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  8:11 [RFC v3] checkpatch: detect missing changes to trace-events Claudio Fontana
2020-09-14 13:44 ` Stefan Hajnoczi
2020-09-14 14:49   ` Claudio Fontana [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=cf51a4d1-f760-dd83-fde8-9e9121daae50@suse.de \
    --to=cfontana@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).