From: no-reply@patchew.org
To: nikunj@linux.vnet.ibm.com
Cc: famz@redhat.com, qemu-ppc@nongnu.org,
david@gibson.dropbear.id.au, rth@twiddle.net,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] POWER9 TCG enablements - part6
Date: Tue, 18 Oct 2016 23:29:53 -0700 (PDT) [thread overview]
Message-ID: <20161019062950.502016.60878@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1476857207-10091-1-git-send-email-nikunj@linux.vnet.ibm.com>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1476857207-10091-1-git-send-email-nikunj@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v2 0/2] POWER9 TCG enablements - part6
=== 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'
1854ac2 target-ppc: implement xxbr[qdwh] instruction
39ffa81 target-ppc: implement vnegw/d instructions
=== OUTPUT BEGIN ===
Checking PATCH 1/2: target-ppc: implement vnegw/d instructions...
Checking PATCH 2/2: target-ppc: implement xxbr[qdwh] instruction...
ERROR: Macros with complex values should be enclosed in parenthesis
#176: FILE: target-ppc/translate/vsx-ops.inc.c:42:
+#define GEN_XX2FORM_EO(name, opc2, opc3, opc4, fl2) \
+GEN_HANDLER2_E_2(name, #name, 0x3C, opc2 | 0, opc3, opc4, 0, PPC_NONE, fl2), \
+GEN_HANDLER2_E_2(name, #name, 0x3C, opc2 | 1, opc3, opc4, 0, PPC_NONE, fl2)
total: 1 errors, 0 warnings, 159 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
next prev parent reply other threads:[~2016-10-19 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 6:06 [Qemu-devel] [PATCH v2 0/2] POWER9 TCG enablements - part6 Nikunj A Dadhania
2016-10-19 6:06 ` [Qemu-devel] [PATCH v2 1/2] target-ppc: implement vnegw/d instructions Nikunj A Dadhania
2016-10-19 8:03 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2016-10-19 16:07 ` [Qemu-devel] " Richard Henderson
2016-10-19 6:06 ` [Qemu-devel] [PATCH v2 2/2] target-ppc: implement xxbr[qdwh] instruction Nikunj A Dadhania
2016-10-19 16:08 ` Richard Henderson
2016-10-19 6:29 ` no-reply [this message]
2016-10-20 0:03 ` [Qemu-devel] [PATCH v2 0/2] POWER9 TCG enablements - part6 David Gibson
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=20161019062950.502016.60878@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=david@gibson.dropbear.id.au \
--cc=famz@redhat.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).