All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: ehabkost@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
	imammedo@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] target-i386: Print warning when mixing [+-]foo and foo=(on|off)
Date: Fri, 21 Oct 2016 12:15:30 -0700 (PDT)	[thread overview]
Message-ID: <20161021191527.502016.73905@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1477075788-26632-1-git-send-email-ehabkost@redhat.com>

Hi,

Your series seems to have some coding style problems. See output below for
more information:

Subject: [Qemu-devel] [PATCH] target-i386: Print warning when mixing [+-]foo and foo=(on|off)
Type: series
Message-id: 1477075788-26632-1-git-send-email-ehabkost@redhat.com

=== TEST SCRIPT BEGIN ===
#!/bin/bash

BASE=base
n=1
total=$(git log --oneline $BASE.. | wc -l)
failed=0

# Useful git options
git config --local diff.renamelimit 0
git config --local diff.renames True

commits="$(git log --format=%H --reverse $BASE..)"
for c in $commits; do
    echo "Checking PATCH $n/$total: $(git show --no-patch --format=%s $c)..."
    if ! git show $c --format=email | ./scripts/checkpatch.pl --mailback -; then
        failed=1
        echo
    fi
    n=$((n+1))
done

exit $failed
=== TEST SCRIPT END ===

Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
Switched to a new branch 'test'
9d8f97d target-i386: Print warning when mixing [+-]foo and foo=(on|off)

=== OUTPUT BEGIN ===
Checking PATCH 1/1: target-i386: Print warning when mixing [+-]foo and foo=(on|off)...
ERROR: Error messages should not contain newlines
#35: FILE: target-i386/cpu.c:2032:
+                         "Don't mix both \"+%s\" and \"%s=%s\"\n"

ERROR: Error messages should not contain newlines
#42: FILE: target-i386/cpu.c:2039:
+                         "Don't mix both \"-%s\" and \"%s=%s\"\n"

ERROR: line over 90 characters
#84: FILE: tests/test-x86-cpuid-compat.c:114:
+    g_test_trap_assert_stderr("*Ambiguous CPU model string. Don't mix both \"-mce\" and \"mce=on\"*");

ERROR: line over 90 characters
#85: FILE: tests/test-x86-cpuid-compat.c:115:
+    g_test_trap_assert_stderr("*Ambiguous CPU model string. Don't mix both \"+cx8\" and \"cx8=off\"*");

ERROR: line over 90 characters
#94: FILE: tests/test-x86-cpuid-compat.c:123:
+    g_test_add_func("/x86/cpuid/parsing-plus-minus/subprocess", test_plus_minus_subprocess);

total: 5 errors, 0 warnings, 73 lines checked

Your patch has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.

=== OUTPUT END ===

Test command exited with code: 1


---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@freelists.org

  parent reply	other threads:[~2016-10-21 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 18:49 [Qemu-devel] [PATCH] target-i386: Print warning when mixing [+-]foo and foo=(on|off) Eduardo Habkost
2016-10-21 19:14 ` no-reply
2016-10-21 19:15 ` no-reply [this message]
2016-10-21 19:31   ` Eduardo Habkost

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=20161021191527.502016.73905@ex-std-node742.prod.rhcloud.com \
    --to=no-reply@patchew.org \
    --cc=ehabkost@redhat.com \
    --cc=famz@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.