All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PULL 0/5] virtio,pci: fixes and updates
Date: Wed, 14 Sep 2016 04:32:57 +0300	[thread overview]
Message-ID: <20160914043236-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20160913212756.19907.35881@ex-std-node742.prod.rhcloud.com>

On Tue, Sep 13, 2016 at 02:27:59PM -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:
> 
> Type: series
> Message-id: 1473798735-6290-1-git-send-email-mst@redhat.com
> Subject: [Qemu-devel] [PULL 0/5] 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
> From https://github.com/patchew-project/qemu
>  * [new tag]         patchew/1473798735-6290-1-git-send-email-mst@redhat.com -> patchew/1473798735-6290-1-git-send-email-mst@redhat.com
> Switched to a new branch 'test'
> e7a4ce2 hw/i386: AMD IOMMU IVRS table
> 69dfd17 hw/i386: Introduce AMD IOMMU
> 577db28 hw/i386/trace-events: Add AMD IOMMU trace events
> da2c51f hw/pci: Prepare for AMD IOMMU
> c64cb29 virtio-bus: Plug devices after features are negotiated
> 
> === OUTPUT BEGIN ===
> Checking PATCH 1/5: virtio-bus: Plug devices after features are negotiated...
> Checking PATCH 2/5: hw/pci: Prepare for AMD IOMMU...
> Checking PATCH 3/5: hw/i386/trace-events: Add AMD IOMMU trace events...
> Checking PATCH 4/5: hw/i386: Introduce AMD IOMMU...
> ERROR: struct MemoryRegionIOMMUOps should normally be const
> #1707: FILE: hw/i386/amd_iommu.h:280:
> +    MemoryRegionIOMMUOps iommu_ops;


I think this is bogus: don't see how a struct field can be const here.

> 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/5: hw/i386: AMD IOMMU IVRS table...
> === 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-09-14  1:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 20:32 [Qemu-devel] [PULL 0/5] virtio,pci: fixes and updates Michael S. Tsirkin
2016-09-13 20:32 ` [Qemu-devel] [PULL 1/5] virtio-bus: Plug devices after features are negotiated Michael S. Tsirkin
2016-09-13 20:32 ` [Qemu-devel] [PULL 2/5] hw/pci: Prepare for AMD IOMMU Michael S. Tsirkin
2016-09-13 20:32 ` [Qemu-devel] [PULL 3/5] hw/i386/trace-events: Add AMD IOMMU trace events Michael S. Tsirkin
2016-09-13 20:32 ` [Qemu-devel] [PULL 4/5] hw/i386: Introduce AMD IOMMU Michael S. Tsirkin
2016-09-13 20:32 ` [Qemu-devel] [PULL 5/5] hw/i386: AMD IOMMU IVRS table Michael S. Tsirkin
2016-09-13 21:27 ` [Qemu-devel] [PULL 0/5] virtio,pci: fixes and updates no-reply
2016-09-14  1:32   ` Michael S. Tsirkin [this message]
2016-09-13 21:31 ` no-reply
2016-09-14  1:31   ` Michael S. Tsirkin
2016-09-14  1:32 ` Michael S. Tsirkin
2016-09-15 13:55   ` Peter Maydell
2016-09-15 15:24     ` Michael S. Tsirkin

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=20160914043236-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=famz@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 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.