All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: quintela@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, lvivier@redhat.com,
	dgilbert@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PULL 0/5] Migration pull request
Date: Sun, 3 Jun 2018 21:29:51 -0700 (PDT)	[thread overview]
Message-ID: <152808659065.396.9065157974177590230@d39dc562802a> (raw)
In-Reply-To: <20180604042156.13812-1-quintela@redhat.com>

Hi,

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

Type: series
Message-id: 20180604042156.13812-1-quintela@redhat.com
Subject: [Qemu-devel] [PULL 0/5] Migration pull request

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

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

git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram

commits="$(git log --format=%H --reverse $BASE..)"
for c in $commits; do
    echo "Checking PATCH $n/$total: $(git log -n 1 --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
 t [tag update]            patchew/20180514065700.22202-1-clg@kaod.org -> patchew/20180514065700.22202-1-clg@kaod.org
 * [new tag]               patchew/20180604042156.13812-1-quintela@redhat.com -> patchew/20180604042156.13812-1-quintela@redhat.com
Switched to a new branch 'test'
99ac0fb20d migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect
7c902253bb migration: remove unnecessary variables len in QIOChannelRDMA
3c1203cb38 migration: Don't activate block devices if using -S
2ecc458546 migration: discard non-migratable RAMBlocks
718b388d4e migration: introduce decompress-error-check

=== OUTPUT BEGIN ===
Checking PATCH 1/5: migration: introduce decompress-error-check...
Checking PATCH 2/5: migration: discard non-migratable RAMBlocks...
ERROR: Macros with multiple statements should be enclosed in a do - while loop
#191: FILE: migration/ram.c:161:
+#define RAMBLOCK_FOREACH_MIGRATABLE(block)             \
+    RAMBLOCK_FOREACH(block)                            \
+        if (!qemu_ram_is_migratable(block)) {} else

ERROR: trailing statements should be on next line
#193: FILE: migration/ram.c:163:
+        if (!qemu_ram_is_migratable(block)) {} else

total: 2 errors, 0 warnings, 273 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 3/5: migration: Don't activate block devices if using -S...
Checking PATCH 4/5: migration: remove unnecessary variables len in QIOChannelRDMA...
Checking PATCH 5/5: migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect...
=== OUTPUT END ===

Test command exited with code: 1


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

  parent reply	other threads:[~2018-06-04  4:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04  4:21 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2018-06-04  4:21 ` [Qemu-devel] [PULL 1/5] migration: introduce decompress-error-check Juan Quintela
2018-06-04  4:21 ` [Qemu-devel] [PULL 2/5] migration: discard non-migratable RAMBlocks Juan Quintela
2018-06-04  4:21 ` [Qemu-devel] [PULL 3/5] migration: Don't activate block devices if using -S Juan Quintela
2018-06-04  4:21 ` [Qemu-devel] [PULL 4/5] migration: remove unnecessary variables len in QIOChannelRDMA Juan Quintela
2018-06-04  4:21 ` [Qemu-devel] [PULL 5/5] migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect Juan Quintela
2018-06-04  4:29 ` no-reply [this message]
2018-06-04  7:30   ` [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2018-06-04 13:24 ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2017-06-14 11:51 [Qemu-devel] [PULL 0/5] Migration PULL request Juan Quintela
2017-06-15 11:56 ` Peter Maydell
2017-05-31  9:15 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2017-06-01 14:50 ` Peter Maydell
2017-05-12 15:52 Juan Quintela
2017-05-15 13:58 ` Stefan Hajnoczi
2017-05-15 14:52   ` Eric Blake
2017-05-15 17:17   ` Juan Quintela
2017-05-16 14:35 ` Stefan Hajnoczi
2015-11-04 12:48 Juan Quintela
2015-11-05 10:48 ` Peter Maydell

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=152808659065.396.9065157974177590230@d39dc562802a \
    --to=no-reply@patchew.org \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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.