From: no-reply@patchew.org
To: jiangshanlai@gmail.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, quintela@redhat.com,
crosthwaite.peter@gmail.com, armbru@redhat.com,
amit.shah@redhat.com, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] add migration capability to bypass the shared memory
Date: Tue, 9 Aug 2016 06:51:18 -0700 (PDT) [thread overview]
Message-ID: <20160809135115.131721.23375@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1470744604-80857-1-git-send-email-jiangshanlai@gmail.com>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Message-id: 1470744604-80857-1-git-send-email-jiangshanlai@gmail.com
Type: series
Subject: [Qemu-devel] [PATCH] add migration capability to bypass the shared memory
=== 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
Switched to a new branch 'test'
e63cdc7 add migration capability to bypass the shared memory
=== OUTPUT BEGIN ===
Checking PATCH 1/1: add migration capability to bypass the shared memory...
ERROR: code indent should never use tabs
#175: FILE: migration/ram.c:626:
+^I migration_dirty_pages += block->used_length >> TARGET_PAGE_BITS;$
ERROR: code indent should never use tabs
#176: FILE: migration/ram.c:627:
+^I}$
ERROR: code indent should never use tabs
#204: FILE: migration/ram.c:1958:
+^I^I migration_bitmap_rcu->bmap, ram_bitmap_pages);$
total: 3 errors, 0 warnings, 137 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-08-09 13:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 12:10 [Qemu-devel] [PATCH] add migration capability to bypass the shared memory Lai Jiangshan
2016-08-09 13:51 ` no-reply [this message]
2016-08-09 19:12 ` Dr. David Alan Gilbert
2016-08-10 0:54 ` [Qemu-devel] [PATCH V2] " Lai Jiangshan
2016-08-10 1:22 ` Fam Zheng
2016-08-10 2:22 ` Li, Liang Z
2016-08-10 3:22 ` Lai Jiangshan
2016-08-10 5:04 ` Li, Liang Z
2016-08-10 9:11 ` Juan Quintela
2016-08-11 7:11 ` Li, Liang Z
2016-08-11 14:31 ` Lai Jiangshan
2016-08-11 14:45 ` Lai Jiangshan
2017-09-21 3:41 ` Zhang Haoyu
2016-08-12 6:48 ` Li, Liang Z
2016-08-12 7:19 ` Lai Jiangshan
2017-09-25 7:42 ` Zhang Haoyu
2017-09-25 12:13 ` Zhang Haoyu
2016-08-10 1:09 ` [Qemu-devel] [PATCH] " Lai Jiangshan
2016-08-10 9:03 ` Juan Quintela
2016-08-30 4:11 ` Lai Jiangshan
2016-11-18 13:01 ` Alexander Graf
2017-01-12 19:19 ` Jianjun Duan
2017-01-13 4:44 ` Lai Jiangshan
2017-01-16 17:38 ` Jianjun Duan
2017-09-21 6:33 ` Zhang Haoyu
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=20160809135115.131721.23375@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=famz@redhat.com \
--cc=jiangshanlai@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).