All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchew Tool <patchew.tool@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] kvm: fix ioeventfd endianness on bi-endian architectures
Date: Fri, 13 Mar 2015 14:30:52 -0700 (PDT)	[thread overview]
Message-ID: <5503570c.94558c0a.1441.ffffd1a4@mx.google.com> (raw)
In-Reply-To: <20150313212337.31142.3991.stgit@bahia.local>


This series passed Patchew automatic testing, but there are some warnings.

Find the log fragments below, or open the following URL to see the full log:

http://qemu.patchew.org/testing/log/<20150313212337.31142.3991.stgit@bahia.local>

----------8<---------


=== Starting docker ===

Copying test script "/home/patchew/tests/qemu-devel.sh"
Starting docker...
docker run --net=none -v /var/tmp/patchew-tester/tmpEMd8Zd:/var/tmp/patchew-test patchew:fedora-20 timeout 3600 /var/tmp/patchew-test/qemu-devel.sh /var/tmp/patchew-test

*** Testing 'coding style check' ***

Checking 0001-kvm--fix-ioeventfd-endianness-on-bi-endian-architectures.patch
command failed with exit code 0
$@
ERROR: space required before the open parenthesis '('
#26: FILE: kvm-all.c:538:
+    switch(size) {

total: 1 errors, 0 warnings, 42 lines checked

0001-kvm--fix-ioeventfd-endianness-on-bi-endian-architectures.patch has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.


*** Testing 'configure' ***

Install prefix    /usr/local
BIOS directory    /usr/local/share/qemu
binary directory  /usr/local/bin
library directory /usr/local/lib
module directory  /usr/local/lib/qemu
libexec directory /usr/local/libexec

  reply	other threads:[~2015-03-13 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 21:23 [Qemu-devel] [PATCH] kvm: fix ioeventfd endianness on bi-endian architectures Greg Kurz
2015-03-13 21:30 ` Patchew Tool [this message]
2015-03-15  9:14   ` Paolo Bonzini
2015-03-17  7:56     ` Greg Kurz

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=5503570c.94558c0a.1441.ffffd1a4@mx.google.com \
    --to=patchew.tool@gmail.com \
    --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.