From: no-reply@patchew.org
To: famz@redhat.com
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com, keith.busch@intel.com, stefanha@redhat.com,
pbonzini@redhat.com, krister@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device
Date: Thu, 6 Jul 2017 07:06:37 -0700 (PDT) [thread overview]
Message-ID: <149934999661.27.13789728207994914021@f0098f8687cc> (raw)
In-Reply-To: <20170705133635.11850-1-famz@redhat.com>
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20170705133635.11850-1-famz@redhat.com
Type: series
Subject: [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device
=== 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
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
Switched to a new branch 'test'
079ea59 block: Move NVMe spec definitions to a separate header
28b0ea5 qemu-img: Map bench buffer
0c5fe62 block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap
bb59e7c block: Introduce bdrv_dma_map and bdrv_dma_unmap
be4dab1 block: Add VFIO based NVMe driver
74c0158 stubs: Add stubs for ram block API
=== OUTPUT BEGIN ===
Checking PATCH 1/6: stubs: Add stubs for ram block API...
Checking PATCH 2/6: block: Add VFIO based NVMe driver...
WARNING: line over 80 characters
#191: FILE: block/nvme-vfio.c:133:
+ if (ioctl(s->device, VFIO_DEVICE_GET_REGION_INFO, &s->bar_region_info[index])) {
WARNING: line over 80 characters
#279: FILE: block/nvme-vfio.c:221:
+static int nvme_vfio_pci_write_config(NVMeVFIOState *s, void *buf, int size, int ofs)
ERROR: Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt
#843: FILE: block/nvme.c:40:
+ volatile uint32_t *doorbell;
ERROR: Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt
#869: FILE: block/nvme.c:66:
+typedef volatile struct {
WARNING: line over 80 characters
#1381: FILE: block/nvme.c:578:
+ error_setg(errp, "Timeout while waiting for device to reset (%ld ms)",
WARNING: line over 80 characters
#1410: FILE: block/nvme.c:607:
+ error_setg(errp, "Timeout while waiting for device to start (%ld ms)",
total: 2 errors, 4 warnings, 1878 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 3/6: block: Introduce bdrv_dma_map and bdrv_dma_unmap...
Checking PATCH 4/6: block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap...
Checking PATCH 5/6: qemu-img: Map bench buffer...
Checking PATCH 6/6: block: Move NVMe spec definitions to a separate header...
=== 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:[~2017-07-06 14:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 13:36 [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device Fam Zheng
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 1/6] stubs: Add stubs for ram block API Fam Zheng
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 2/6] block: Add VFIO based NVMe driver Fam Zheng
2017-07-06 17:38 ` Keith Busch
2017-07-06 23:27 ` Fam Zheng
2017-07-07 10:06 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2017-07-07 17:15 ` [Qemu-devel] " Stefan Hajnoczi
2017-07-10 14:55 ` Stefan Hajnoczi
2017-07-12 2:14 ` Fam Zheng
2017-07-12 10:49 ` Stefan Hajnoczi
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 3/6] block: Introduce bdrv_dma_map and bdrv_dma_unmap Fam Zheng
2017-07-10 14:57 ` Stefan Hajnoczi
2017-07-10 15:07 ` Stefan Hajnoczi
2017-07-10 15:08 ` Paolo Bonzini
2017-07-11 10:05 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-11 10:28 ` Paolo Bonzini
2017-07-12 1:07 ` Fam Zheng
2017-07-12 14:03 ` Paolo Bonzini
2017-07-14 13:37 ` Stefan Hajnoczi
2017-07-14 13:46 ` Paolo Bonzini
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 4/6] block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap Fam Zheng
2017-07-10 14:59 ` Stefan Hajnoczi
2017-07-10 15:09 ` Paolo Bonzini
2017-07-11 10:04 ` Stefan Hajnoczi
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 5/6] qemu-img: Map bench buffer Fam Zheng
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 6/6] block: Move NVMe spec definitions to a separate header Fam Zheng
2017-07-05 13:39 ` Paolo Bonzini
2017-07-10 15:01 ` Stefan Hajnoczi
2017-07-05 13:41 ` [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device Paolo Bonzini
2017-07-06 14:06 ` no-reply [this message]
2017-07-06 14:22 ` Paolo Bonzini
2017-07-06 14:36 ` Fam Zheng
2017-07-06 14:44 ` Paolo Bonzini
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=149934999661.27.13789728207994914021@f0098f8687cc \
--to=no-reply@patchew.org \
--cc=famz@redhat.com \
--cc=keith.busch@intel.com \
--cc=krister@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).