From: no-reply@patchew.org
To: mst@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PULL v2 0/6] virtio,pci: fixes and updates
Date: Thu, 15 Sep 2016 09:25:51 -0700 (PDT) [thread overview]
Message-ID: <20160915162548.19907.1431@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1473952956-16264-1-git-send-email-mst@redhat.com>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1473952956-16264-1-git-send-email-mst@redhat.com
Subject: [Qemu-devel] [PULL v2 0/6] virtio,pci: fixes and updates
=== 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
Switched to a new branch 'test'
6e5404e MAINTAINERS: add virtio-* tests
891e449 hw/i386: AMD IOMMU IVRS table
2e128a0 hw/i386: Introduce AMD IOMMU
6f5a9ae hw/i386/trace-events: Add AMD IOMMU trace events
1ee8f53 hw/pci: Prepare for AMD IOMMU
aa2f6bf virtio-bus: Plug devices after features are negotiated
=== OUTPUT BEGIN ===
Checking PATCH 1/6: virtio-bus: Plug devices after features are negotiated...
Checking PATCH 2/6: hw/pci: Prepare for AMD IOMMU...
Checking PATCH 3/6: hw/i386/trace-events: Add AMD IOMMU trace events...
Checking PATCH 4/6: hw/i386: Introduce AMD IOMMU...
ERROR: struct MemoryRegionIOMMUOps should normally be const
#1707: FILE: hw/i386/amd_iommu.h:280:
+ MemoryRegionIOMMUOps iommu_ops;
total: 1 errors, 0 warnings, 1677 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 5/6: hw/i386: AMD IOMMU IVRS table...
Checking PATCH 6/6: MAINTAINERS: add virtio-* tests...
=== 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-15 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 15:22 [Qemu-devel] [PULL v2 0/6] virtio,pci: fixes and updates Michael S. Tsirkin
2016-09-15 15:22 ` [Qemu-devel] [PULL v2 1/6] virtio-bus: Plug devices after features are negotiated Michael S. Tsirkin
2016-09-15 15:22 ` [Qemu-devel] [PULL v2 2/6] hw/pci: Prepare for AMD IOMMU Michael S. Tsirkin
2016-09-15 15:22 ` [Qemu-devel] [PULL v2 3/6] hw/i386/trace-events: Add AMD IOMMU trace events Michael S. Tsirkin
2016-09-15 15:22 ` [Qemu-devel] [PULL v2 4/6] hw/i386: Introduce AMD IOMMU Michael S. Tsirkin
2016-09-15 15:22 ` [Qemu-devel] [PULL v2 5/6] hw/i386: AMD IOMMU IVRS table Michael S. Tsirkin
2016-09-15 15:23 ` [Qemu-devel] [PULL v2 6/6] MAINTAINERS: add virtio-* tests Michael S. Tsirkin
2016-09-15 16:25 ` no-reply [this message]
2016-09-15 16:36 ` [Qemu-devel] [PULL v2 0/6] virtio,pci: fixes and updates Michael S. Tsirkin
2016-09-15 18:35 ` 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=20160915162548.19907.1431@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=famz@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).