From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: wangjie88@huawei.com, famz@redhat.com, qemu-block@nongnu.org,
kwolf@redhat.com, subo7@huawei.com, eric.fangyi@huawei.com,
stefanha@redhat.com, wu.wubin@huawei.com
Subject: Re: [Qemu-devel] [PATCH] test: add drive-mirror qtest
Date: Tue, 6 Sep 2016 12:14:02 -0400 [thread overview]
Message-ID: <20160906161402.GB1311@localhost.localdomain> (raw)
In-Reply-To: <20160906155954.76034.66133@ex-std-node742.prod.rhcloud.com>
On Tue, Sep 06, 2016 at 08:59:58AM -0700, no-reply@ec2-52-6-146-230.compute-1.amazonaws.com wrote:
> Hi,
>
> Your series seems to have some coding style problems. See output below for
> more information:
>
> Subject: [Qemu-devel] [PATCH] test: add drive-mirror qtest
> Type: series
> Message-id: 1473170519-72598-1-git-send-email-wangjie88@huawei.com
>
Hi Jie,
Thanks for the patch.
You can check for this sort of issue by running the 'checkpatch.pl' utility
on your patches, prior to submission... e.g.:
./scripts/checkpatch.pl patchfilename.patch
Also, when submitting a new patch revision, it should be indicated in the
subject line, e.g.:
[PATCH v2] test: add drive-mirror qtest
Regarding the patch itself, is there something this does that is not covered
in the io-test case 041 (tests/qemu-iotest/041)?
Thanks,
Jeff
> === 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
> From https://github.com/patchew-project/qemu
> * [new tag] patchew/1473170519-72598-1-git-send-email-wangjie88@huawei.com -> patchew/1473170519-72598-1-git-send-email-wangjie88@huawei.com
> * [new tag] patchew/1473171997-11359-1-git-send-email-berrange@redhat.com -> patchew/1473171997-11359-1-git-send-email-berrange@redhat.com
> * [new tag] patchew/1473173750-11761-1-git-send-email-marcel@redhat.com -> patchew/1473173750-11761-1-git-send-email-marcel@redhat.com
> Switched to a new branch 'test'
> d44ab2b test: add drive-mirror qtest
>
> === OUTPUT BEGIN ===
> Checking PATCH 1/1: test: add drive-mirror qtest...
> ERROR: do not set execute permissions for source files
> #31: FILE: tests/drive-mirror-test.c
>
> total: 1 errors, 0 warnings, 111 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-09-06 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 14:01 [Qemu-devel] [PATCH] test: add drive-mirror qtest Jie Wang
2016-09-06 15:59 ` no-reply
2016-09-06 16:14 ` Jeff Cody [this message]
2016-09-06 16:10 ` 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=20160906161402.GB1311@localhost.localdomain \
--to=jcody@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=subo7@huawei.com \
--cc=wangjie88@huawei.com \
--cc=wu.wubin@huawei.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).