All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: vijay.kilari@gmail.com
Cc: peter.maydell@linaro.org, famz@redhat.com,
	vijay.kilari@gmail.com, Prasun.Kapoor@cavium.com,
	p.fedin@samsung.com, qemu-devel@nongnu.org,
	Vijaya.Kumar@cavium.com, qemu-arm@nongnu.org,
	pbonzini@redhat.com
Subject: Re: [Qemu-arm] [Qemu-devel] [RFC PATCH v2 0/2] GICv3 live migration support
Date: Mon, 8 Aug 2016 09:58:48 -0700 (PDT)	[thread overview]
Message-ID: <E1bWntB-0005fM-7f@eggs.gnu.org> (raw)
In-Reply-To: <1470675071-23677-1-git-send-email-vijay.kilari@gmail.com>

Hi,

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

Message-id: 1470675071-23677-1-git-send-email-vijay.kilari@gmail.com
Type: series
Subject: [Qemu-devel] [RFC PATCH v2 0/2] GICv3 live migration support

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

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

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
From https://github.com/patchew-project/qemu
 * [new tag]         patchew/1470675071-23677-1-git-send-email-vijay.kilari@gmail.com -> patchew/1470675071-23677-1-git-send-email-vijay.kilari@gmail.com
Switched to a new branch 'test'
52635e4 hw/intc/arm_gicv3_kvm: Implement get/put functions
15053e8 kernel: Add definitions for GICv3 attributes

=== OUTPUT BEGIN ===
Checking PATCH 1/2: kernel: Add definitions for GICv3 attributes...
ERROR: code indent should never use tabs
#22: FILE: linux-headers/asm-arm64/kvm.h:183:
+^I(ARM64_SYS_REG_SHIFT_MASK(op0, OP0) | \$

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                      ^

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                          ^

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                              ^

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                                  ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                           ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                               ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                                   ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                                       ^

total: 9 errors, 0 warnings, 38 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.

Checking PATCH 2/2: hw/intc/arm_gicv3_kvm: Implement get/put functions...
ERROR: do not use C99 // comments
#291: FILE: hw/intc/arm_gicv3_kvm.c:300:
+        // TODO: there is no kernel API for reading/writing c->level

ERROR: do not use C99 // comments
#347: FILE: hw/intc/arm_gicv3_kvm.c:356:
+    // TODO: there is no kernel API for reading/writing s->level

total: 2 errors, 0 warnings, 512 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

WARNING: multiple messages have this Message-ID (diff)
From: no-reply@patchew.org
To: vijay.kilari@gmail.com
Cc: famz@redhat.com, qemu-arm@nongnu.org, peter.maydell@linaro.org,
	pbonzini@redhat.com, Prasun.Kapoor@cavium.com,
	p.fedin@samsung.com, qemu-devel@nongnu.org,
	Vijaya.Kumar@cavium.com
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/2] GICv3 live migration support
Date: Mon, 8 Aug 2016 09:58:48 -0700 (PDT)	[thread overview]
Message-ID: <E1bWntB-0005fM-7f@eggs.gnu.org> (raw)
In-Reply-To: <1470675071-23677-1-git-send-email-vijay.kilari@gmail.com>

Hi,

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

Message-id: 1470675071-23677-1-git-send-email-vijay.kilari@gmail.com
Type: series
Subject: [Qemu-devel] [RFC PATCH v2 0/2] GICv3 live migration support

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

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

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
From https://github.com/patchew-project/qemu
 * [new tag]         patchew/1470675071-23677-1-git-send-email-vijay.kilari@gmail.com -> patchew/1470675071-23677-1-git-send-email-vijay.kilari@gmail.com
Switched to a new branch 'test'
52635e4 hw/intc/arm_gicv3_kvm: Implement get/put functions
15053e8 kernel: Add definitions for GICv3 attributes

=== OUTPUT BEGIN ===
Checking PATCH 1/2: kernel: Add definitions for GICv3 attributes...
ERROR: code indent should never use tabs
#22: FILE: linux-headers/asm-arm64/kvm.h:183:
+^I(ARM64_SYS_REG_SHIFT_MASK(op0, OP0) | \$

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                      ^

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                          ^

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                              ^

ERROR: space required after that ',' (ctx:VxV)
#47: FILE: linux-headers/asm-arm64/kvm.h:211:
+#define   KVM_DEV_ARM_VGIC_SYSREG(op0,op1,crn,crm,op2) \
                                                  ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                           ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                               ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                                   ^

ERROR: space required after that ',' (ctx:VxV)
#48: FILE: linux-headers/asm-arm64/kvm.h:212:
+                                       __ARM64_SYS_REG(op0,op1,crn,crm,op2)
                                                                       ^

total: 9 errors, 0 warnings, 38 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.

Checking PATCH 2/2: hw/intc/arm_gicv3_kvm: Implement get/put functions...
ERROR: do not use C99 // comments
#291: FILE: hw/intc/arm_gicv3_kvm.c:300:
+        // TODO: there is no kernel API for reading/writing c->level

ERROR: do not use C99 // comments
#347: FILE: hw/intc/arm_gicv3_kvm.c:356:
+    // TODO: there is no kernel API for reading/writing s->level

total: 2 errors, 0 warnings, 512 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

  parent reply	other threads:[~2016-08-08 16:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 16:51 [Qemu-devel] [RFC PATCH v2 0/2] GICv3 live migration support vijay.kilari
2016-08-08 16:51 ` vijay.kilari
2016-08-08 16:51 ` [Qemu-arm] [RFC PATCH v2 1/2] kernel: Add definitions for GICv3 attributes vijay.kilari
2016-08-08 16:51   ` [Qemu-devel] " vijay.kilari
2016-08-08 16:51 ` [Qemu-devel] [RFC PATCH v2 2/2] hw/intc/arm_gicv3_kvm: Implement get/put functions vijay.kilari
2016-08-08 16:51   ` vijay.kilari
2016-08-08 16:57   ` [Qemu-arm] " Peter Maydell
2016-08-08 16:57     ` [Qemu-devel] " Peter Maydell
2016-08-09  6:52     ` [Qemu-arm] " Vijay Kilari
2016-08-09  6:52       ` [Qemu-devel] " Vijay Kilari
2016-08-08 16:58 ` no-reply [this message]
2016-08-08 16:58   ` [Qemu-devel] [RFC PATCH v2 0/2] GICv3 live migration support no-reply

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=E1bWntB-0005fM-7f@eggs.gnu.org \
    --to=no-reply@patchew.org \
    --cc=Prasun.Kapoor@cavium.com \
    --cc=Vijaya.Kumar@cavium.com \
    --cc=famz@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vijay.kilari@gmail.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.