From: no-reply@patchew.org
To: skrtbhtngr@gmail.com
Cc: qemu-devel@nongnu.org, yuval.shaia@oracle.com
Subject: Re: [Qemu-devel] [RFC 0/1] Add live migration support to the PVRDMA device
Date: Fri, 21 Jun 2019 10:55:31 -0700 (PDT) [thread overview]
Message-ID: <156113973041.4070.6979056140536397914@ce79690b2cb9> (raw)
In-Reply-To: <20190621144541.13770-1-skrtbhtngr@gmail.com>
Patchew URL: https://patchew.org/QEMU/20190621144541.13770-1-skrtbhtngr@gmail.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [RFC 0/1] Add live migration support to the PVRDMA device
Message-id: 20190621144541.13770-1-skrtbhtngr@gmail.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
./scripts/checkpatch.pl --mailback base..
=== TEST SCRIPT END ===
Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
Switched to a new branch 'test'
21c2b30 hw/pvrdma: Add live migration support
=== OUTPUT BEGIN ===
ERROR: do not use C99 // comments
#50: FILE: hw/rdma/vmw/pvrdma_main.c:610:
+ // Remap DSR
ERROR: do not use C99 // comments
#60: FILE: hw/rdma/vmw/pvrdma_main.c:620:
+ // Remap cmd slot
WARNING: line over 80 characters
#62: FILE: hw/rdma/vmw/pvrdma_main.c:622:
+ dev->dsr_info.req = rdma_pci_dma_map(pci_dev, dev->dsr_info.dsr->cmd_slot_dma,
ERROR: do not use C99 // comments
#70: FILE: hw/rdma/vmw/pvrdma_main.c:630:
+ // Remap rsp slot
WARNING: line over 80 characters
#72: FILE: hw/rdma/vmw/pvrdma_main.c:632:
+ dev->dsr_info.rsp = rdma_pci_dma_map(pci_dev, dev->dsr_info.dsr->resp_slot_dma,
total: 3 errors, 2 warnings, 77 lines checked
Commit 21c2b3077a6c (hw/pvrdma: Add live migration support) has style problems, please review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
=== OUTPUT END ===
Test command exited with code: 1
The full log is available at
http://patchew.org/logs/20190621144541.13770-1-skrtbhtngr@gmail.com/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2019-06-21 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:45 [Qemu-devel] [RFC 0/1] Add live migration support to the PVRDMA device Sukrit Bhatnagar
2019-06-21 14:45 ` [Qemu-devel] [RFC 1/1] hw/pvrdma: Add live migration support Sukrit Bhatnagar
2019-06-25 15:32 ` Yuval Shaia
2019-06-28 11:26 ` Dr. David Alan Gilbert
2019-06-29 12:45 ` Sukrit Bhatnagar
2019-06-30 8:13 ` Yuval Shaia
2019-07-01 2:15 ` Sukrit Bhatnagar
2019-07-01 12:08 ` Yuval Shaia
2019-07-08 10:54 ` Dr. David Alan Gilbert
2019-06-25 15:38 ` Yuval Shaia
2019-06-21 17:55 ` no-reply [this message]
2019-06-25 8:14 ` [Qemu-devel] [RFC 0/1] Add live migration support to the PVRDMA device Marcel Apfelbaum
2019-06-25 8:39 ` Dmitry Fleytman
2019-06-25 8:49 ` Marcel Apfelbaum
2019-06-25 9:11 ` Dr. David Alan Gilbert
2019-06-25 11:39 ` Marcel Apfelbaum
2019-06-25 10:25 ` Dmitry Fleytman
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=156113973041.4070.6979056140536397914@ce79690b2cb9 \
--to=no-reply@patchew.org \
--cc=qemu-devel@nongnu.org \
--cc=skrtbhtngr@gmail.com \
--cc=yuval.shaia@oracle.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).