qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: ashmit602@gmail.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
	kwolf@redhat.com, armbru@redhat.com, berrange@redhat.com,
	ashish.mittal@veritas.com, stefanha@gmail.com,
	Ketan.Nilangekar@veritas.com, Abhijit.Dey@veritas.com
Subject: Re: [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support
Date: Sat, 13 Aug 2016 21:41:40 -0700 (PDT)	[thread overview]
Message-ID: <20160814044135.482798.96356@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1471149312-28148-1-git-send-email-ashish.mittal@veritas.com>

Hi,

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

Message-id: 1471149312-28148-1-git-send-email-ashish.mittal@veritas.com
Subject: [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support
Type: series

=== 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/1471149312-28148-1-git-send-email-ashish.mittal@veritas.com -> patchew/1471149312-28148-1-git-send-email-ashish.mittal@veritas.com
Switched to a new branch 'test'
7b11227 block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

=== OUTPUT BEGIN ===
Checking PATCH 1/1: block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support...
WARNING: line over 80 characters
#305: FILE: block/vxhs.c:212:
+            trace_vxhs_iio_callback_fail(reason, acb, acb->segments, acb->size, error);

WARNING: line over 80 characters
#341: FILE: block/vxhs.c:248:
+        trace_vxhs_iio_callback_ready(((BDRVVXHSState *)ctx)->vdisk_guid, error);

ERROR: spaces required around that '+' (ctx:VxV)
#608: FILE: block/vxhs.c:515:
+            trace_vxhs_parse_json_hostinfo(i+1, vxhsconf->host, vxhsconf->port);
                                             ^

ERROR: spaces required around that '==' (ctx:VxV)
#669: FILE: block/vxhs.c:576:
+        if (i==0 && (strstr(uri->path, "vxhs") == NULL)) {
              ^

ERROR: spaces required around that '+' (ctx:VxV)
#670: FILE: block/vxhs.c:577:
+            conf->vdisk_id = g_new0(char, strlen(uri->path)+3);
                                                            ^

ERROR: spaces required around that '+' (ctx:VxV)
#675: FILE: block/vxhs.c:582:
+        trace_vxhs_parse_uri_hostinfo(i+1, vxhsconf->host, vxhsconf->port);
                                        ^

ERROR: suspect code indent for conditional statements (4, 4)
#1265: FILE: block/vxhs.c:1172:
+    if (res != 0) {
+    trace_vxhs_switch_storage_agent_failed(

ERROR: g_free(NULL) is safe this check is probably not required
#1379: FILE: block/vxhs.c:1286:
+    if (of_vsa_addr) {
+        g_free(of_vsa_addr);

ERROR: g_free(NULL) is safe this check is probably not required
#1382: FILE: block/vxhs.c:1289:
+    if (file_name) {
+        g_free(file_name);

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

  reply	other threads:[~2016-08-14  4:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14  4:35 [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support Ashish Mittal
2016-08-14  4:41 ` no-reply [this message]
2016-08-14  4:43 ` no-reply
2016-08-15 10:20 ` Daniel P. Berrange
2016-08-15 10:47   ` Kevin Wolf
2016-08-15 10:54     ` Daniel P. Berrange
2016-08-17 11:20       ` Paolo Bonzini
2016-08-23 23:28     ` ashish mittal
2016-08-15 16:29   ` ashish mittal
2016-08-17 11:22     ` Paolo Bonzini
2016-08-17 21:58       ` ashish mittal
2016-08-20 18:42         ` ashish mittal
2016-08-23 21:58           ` Stefan Hajnoczi
2016-08-23 22:22             ` ashish mittal
2016-11-15 19:02               ` ashish mittal
2016-11-15 20:48                 ` Stefan Hajnoczi
2016-11-15 20:51                   ` ashish mittal
2017-02-07 23:20                     ` ashish mittal
2016-08-23 22:57   ` ashish mittal

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=20160814044135.482798.96356@ex-std-node742.prod.rhcloud.com \
    --to=no-reply@patchew.org \
    --cc=Abhijit.Dey@veritas.com \
    --cc=Ketan.Nilangekar@veritas.com \
    --cc=armbru@redhat.com \
    --cc=ashish.mittal@veritas.com \
    --cc=ashmit602@gmail.com \
    --cc=berrange@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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).