All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: peter.maydell@linaro.org,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] checkpatch: enforce process for expected files
Date: Mon, 16 Mar 2020 12:17:55 +0100	[thread overview]
Message-ID: <20200316121755.45fa97c2@redhat.com> (raw)
In-Reply-To: <20200315113323.526984-1-mst@redhat.com>

On Sun, 15 Mar 2020 07:35:46 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> If the process documented in tests/qtest/bios-tables-test.c
> is followed, then same patch never touches both expected
> files and code. Teach checkpatch to enforce this rule.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Tested-by: Igor Mammedov <imammedo@redhat.com>

> ---
> 
> Peter, Igor what do you think?
> 
>  scripts/checkpatch.pl | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index b27e4ff5e9..96583e3fff 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -35,6 +35,8 @@ my $summary_file = 0;
>  my $root;
>  my %debug;
>  my $help = 0;
> +my $testexpected;
> +my $nontestexpected;
>  
>  sub help {
>  	my ($exitcode) = @_;
> @@ -1256,6 +1258,26 @@ sub WARN {
>  	}
>  }
>  
> +# According to tests/qtest/bios-tables-test.c: do not
> +# change expected file in the same commit with adding test
> +sub checkfilename {
> +	my ($name) = @_;
> +        if ($name =~ m#^tests/data/acpi/# and
> +            # make exception for a shell script that rebuilds the files
> +            not $name =~ m#^\.sh$# or
> +            $name =~ m#^tests/qtest/bios-tables-test-allowed-diff.h$#) {
> +            $testexpected = $name;
> +        } else {
> +            $nontestexpected = $name;
> +        }
> +        if (defined $testexpected and defined $nontestexpected) {
> +            ERROR("Do not add expected files together with tests, " .
> +                  "follow instructions in " .
> +                  "tests/qtest/bios-tables-test.c: both " .
> +                  $testexpected . " and " . $nontestexpected . " found\n");
> +        }
> +}
> +
>  sub process {
>  	my $filename = shift;
>  
> @@ -1431,9 +1453,11 @@ sub process {
>  		if ($line =~ /^diff --git.*?(\S+)$/) {
>  			$realfile = $1;
>  			$realfile =~ s@^([^/]*)/@@ if (!$file);
> +                        checkfilename($realfile);
>  		} elsif ($line =~ /^\+\+\+\s+(\S+)/) {
>  			$realfile = $1;
>  			$realfile =~ s@^([^/]*)/@@ if (!$file);
> +                        checkfilename($realfile);
>  
>  			$p1_prefix = $1;
>  			if (!$file && $tree && $p1_prefix ne '' &&



      parent reply	other threads:[~2020-03-16 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 11:35 [PATCH] checkpatch: enforce process for expected files Michael S. Tsirkin
2020-03-16  9:54 ` Stefan Hajnoczi
2020-03-16 11:17 ` Igor Mammedov [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=20200316121755.45fa97c2@redhat.com \
    --to=imammedo@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.