From: Paul Durrant <Paul.Durrant@citrix.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "famz@redhat.com" <famz@redhat.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] xen-hvm: use new resource mapping API
Date: Wed, 9 May 2018 16:05:37 +0000 [thread overview]
Message-ID: <82906d30c1854e13bd7986af99eb1d98@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <152588171396.2703.471985236583323449@71c20359a636>
> -----Original Message-----
> From: no-reply@patchew.org [mailto:no-reply@patchew.org]
> Sent: 09 May 2018 17:02
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: famz@redhat.com; qemu-devel@nongnu.org; xen-
> devel@lists.xenproject.org; Paul Durrant <Paul.Durrant@citrix.com>
> Subject: Re: [Qemu-devel] [PATCH 0/2] xen-hvm: use new resource mapping
> API
>
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Type: series
> Message-id: 20180509154604.25530-1-paul.durrant@citrix.com
> Subject: [Qemu-devel] [PATCH 0/2] xen-hvm: use new resource mapping
> API
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
>
> BASE=base
> n=1
> total=$(git log --oneline $BASE.. | wc -l)
> failed=0
>
> git config --local diff.renamelimit 0
> git config --local diff.renames True
> git config --local diff.algorithm histogram
>
> commits="$(git log --format=%H --reverse $BASE..)"
> for c in $commits; do
> echo "Checking PATCH $n/$total: $(git log -n 1 --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/20180509154604.25530-1-
> paul.durrant@citrix.com -> patchew/20180509154604.25530-1-
> paul.durrant@citrix.com
> * [new tag] patchew/20180509154849.27979-1-
> richard.henderson@linaro.org -> patchew/20180509154849.27979-1-
> richard.henderson@linaro.org
> * [new tag] patchew/20180509154949.8206-1-mreitz@redhat.com ->
> patchew/20180509154949.8206-1-mreitz@redhat.com
> Switched to a new branch 'test'
> 16691ff49e xen-hvm: try to use xenforeignmemory_map_resource() to map
> ioreq pages
> d4bcd68252 xen-hvm: create separate function for ioreq server initialization
>
> === OUTPUT BEGIN ===
> Checking PATCH 1/2: xen-hvm: create separate function for ioreq server
> initialization...
> Checking PATCH 2/2: xen-hvm: try to use
> xenforeignmemory_map_resource() to map ioreq pages...
> ERROR: spaces required around that '*' (ctx:WxV)
> #164: FILE: include/hw/xen/xen_common.h:128:
> + xenforeignmemory_handle *fmem, domid_t domid, unsigned int type,
> ^
>
> total: 1 errors, 0 warnings, 138 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.
This style warning appears to be spurious.
Paul
>
> === OUTPUT END ===
>
> Test command exited with code: 1
>
>
> ---
> Email generated automatically by Patchew [http://patchew.org/].
> Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2018-05-09 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:46 [Qemu-devel] [PATCH 0/2] xen-hvm: use new resource mapping API Paul Durrant
2018-05-09 15:46 ` [Qemu-devel] [PATCH 1/2] xen-hvm: create separate function for ioreq server initialization Paul Durrant
2018-05-09 15:46 ` [Qemu-devel] [PATCH 2/2] xen-hvm: try to use xenforeignmemory_map_resource() to map ioreq pages Paul Durrant
2018-05-09 16:01 ` [Qemu-devel] [PATCH 0/2] xen-hvm: use new resource mapping API no-reply
2018-05-09 16:05 ` Paul Durrant [this message]
2018-05-09 17:26 ` Eric Blake
2018-05-10 8:29 ` Paul Durrant
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=82906d30c1854e13bd7986af99eb1d98@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xenproject.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).