qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Matt Hines <mhines@scalecomputing.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "fam@euphon.net" <fam@euphon.net>,
	"mdroth@linux.vnet.ibm.com" <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3] QGA: Fix guest-get-fsinfo PCI addresscollection in Windows
Date: Wed, 27 Feb 2019 17:41:19 -0800	[thread overview]
Message-ID: <5c773c41.1c69fb81.68974.a5a0@mx.google.com> (raw)
In-Reply-To: <154895722053.23946.2175068699085740175@ebba9967afc0>

ping



From: no-reply@patchew.org
Sent: Thursday, January 31, 2019 9:53
To: mhines@scalecomputing.com
Cc: fam@euphon.net; qemu-devel@nongnu.org; mhines@scalecomputing.com; mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3] QGA: Fix guest-get-fsinfo PCI addresscollection in Windows

Patchew URL: https://patchew.org/QEMU/20190128223056.19452-1-mhines@scalecomputing.com/



Hi,

This series seems to have some coding style problems. See output below for
more information:

Subject: [Qemu-devel] [PATCH v3] QGA: Fix guest-get-fsinfo PCI address collection in Windows
Type: series
Message-id: 20190128223056.19452-1-mhines@scalecomputing.com

=== TEST SCRIPT BEGIN ===
#!/bin/bash
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'
6805362916 QGA: Fix guest-get-fsinfo PCI address collection in Windows

=== OUTPUT BEGIN ===
WARNING: Block comments should align the * on each line
#198: FILE: qga/commands-win32.c:592:
+            /*
+            * CM API used here as opposed to

WARNING: line over 80 characters
#302: FILE: qga/commands-win32.c:661:
+            /* There is no need to allocate buffer in the next functions. The size

WARNING: Block comments use a leading /* on a separate line
#302: FILE: qga/commands-win32.c:661:
+            /* There is no need to allocate buffer in the next functions. The size

WARNING: Block comments should align the * on each line
#303: FILE: qga/commands-win32.c:662:
+            /* There is no need to allocate buffer in the next functions. The size
+            * is known and ULONG according to

ERROR: spaces required around that '&' (ctx:VxV)
#308: FILE: qga/commands-win32.c:667:
+                  &type, (PBYTE)&bus, size, NULL)) {
                                 ^

WARNING: Block comments use a leading /* on a separate line
#326: FILE: qga/commands-win32.c:673:
+            /* The function retrieves the device's address. This value will be

WARNING: Block comments use a trailing */ on a separate line
#327: FILE: qga/commands-win32.c:674:
+            * transformed into device function and number */

WARNING: Block comments should align the * on each line
#327: FILE: qga/commands-win32.c:674:
+            /* The function retrieves the device's address. This value will be
+            * transformed into device function and number */

ERROR: spaces required around that '&' (ctx:VxV)
#330: FILE: qga/commands-win32.c:677:
+                    &type, (PBYTE)&addr, size, NULL)) {
                                   ^

WARNING: Block comments use a leading /* on a separate line
#336: FILE: qga/commands-win32.c:683:
+            /* This call returns UINumber of DEVICE_CAPABILITIES structure.

WARNING: Block comments use a trailing */ on a separate line
#337: FILE: qga/commands-win32.c:684:
+            * This number is typically a user-perceived slot number. */

WARNING: Block comments should align the * on each line
#337: FILE: qga/commands-win32.c:684:
+            /* This call returns UINumber of DEVICE_CAPABILITIES structure.
+            * This number is typically a user-perceived slot number. */

ERROR: spaces required around that '&' (ctx:VxV)
#340: FILE: qga/commands-win32.c:687:
+                    &type, (PBYTE)&slot, size, NULL)) {
                                   ^

WARNING: Block comments use a leading /* on a separate line
#346: FILE: qga/commands-win32.c:693:
+            /* SetupApi gives us the same information as driver with

WARNING: Block comments should align the * on each line
#347: FILE: qga/commands-win32.c:694:
+            /* SetupApi gives us the same information as driver with
+            * IoGetDeviceProperty. According to Microsoft

WARNING: Block comments use a trailing */ on a separate line
#351: FILE: qga/commands-win32.c:698:
+            * SPDRP_ADDRESS is propertyAddress, so we do the same.*/

total: 3 errors, 13 warnings, 407 lines checked

Commit 680536291660 (QGA: Fix guest-get-fsinfo PCI address collection in Windows) 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/20190128223056.19452-1-mhines@scalecomputing.com/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

      reply	other threads:[~2019-02-28  1:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  9:03 [Qemu-devel] [PATCH] QGA: Fix guest-get-fsinfo PCI address collection in Windows mhines
2019-01-14  9:24 ` no-reply
2019-01-14 19:41 ` Eric Blake
2019-01-14 20:37   ` [Qemu-devel] [PATCH] QGA: Fix guest-get-fsinfo PCI addresscollection " Matt Hines
2019-01-15 16:57 ` [Qemu-devel] [PATCH v2] QGA: Fix guest-get-fsinfo PCI address collection " mhines
2019-01-21  4:31   ` no-reply
2019-01-21  4:42   ` no-reply
2019-01-24 17:56 ` [Qemu-devel] [PATCH] " Michael Roth
2019-01-24 17:59   ` [Qemu-devel] [PATCH] QGA: Fix guest-get-fsinfo PCI address collection inWindows Matt Hines
2019-01-28 22:30 ` [Qemu-devel] [PATCH v3] QGA: Fix guest-get-fsinfo PCI address collection in Windows mhines
2019-01-31 17:53   ` no-reply
2019-02-28  1:41     ` Matt Hines [this message]

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=5c773c41.1c69fb81.68974.a5a0@mx.google.com \
    --to=mhines@scalecomputing.com \
    --cc=fam@euphon.net \
    --cc=mdroth@linux.vnet.ibm.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 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).