All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: huangy81@chinatelecom.cn
Cc: ehabkost@redhat.com, quintela@redhat.com,
	huangy81@chinatelecom.cn, qemu-devel@nongnu.org,
	peterx@redhat.com, dgilbert@redhat.com, zhengchuan@huawei.com,
	pbonzini@redhat.com
Subject: Re: [PATCH v5 0/6] support dirtyrate at the granualrity of vcpu
Date: Thu, 17 Jun 2021 06:27:46 -0700 (PDT)	[thread overview]
Message-ID: <162393646568.30552.12017277222021052187@7c66fb7bc3ab> (raw)
In-Reply-To: <cover.1623934182.git.huangy81@chinatelecom.cn>

Patchew URL: https://patchew.org/QEMU/cover.1623934182.git.huangy81@chinatelecom.cn/



Hi,

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

Type: series
Message-id: cover.1623934182.git.huangy81@chinatelecom.cn
Subject: [PATCH v5 0/6] support dirtyrate at the granualrity of vcpu 

=== 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
From https://github.com/patchew-project/qemu
 * [new tag]         patchew/cover.1623934182.git.huangy81@chinatelecom.cn -> patchew/cover.1623934182.git.huangy81@chinatelecom.cn
Switched to a new branch 'test'
7c3806f migration/dirtyrate: implement dirty-ring dirtyrate calculation
de17d86 migration/dirtyrate: move init step of calculation to main thread
bcdab9c migration/dirtyrate: adjust order of registering thread
7df987c migration/dirtyrate: introduce struct and adjust DirtyRateStat
4cb2069 memory: make global_dirty_tracking a bitmask
1eaf085 memory: rename global_dirty_log to global_dirty_tracking

=== OUTPUT BEGIN ===
1/6 Checking commit 1eaf085f9a24 (memory: rename global_dirty_log to global_dirty_tracking)
2/6 Checking commit 4cb20690ee05 (memory: make global_dirty_tracking a bitmask)
3/6 Checking commit 7df987cc88c8 (migration/dirtyrate: introduce struct and adjust DirtyRateStat)
4/6 Checking commit bcdab9c720b2 (migration/dirtyrate: adjust order of registering thread)
5/6 Checking commit de17d8630d2f (migration/dirtyrate: move init step of calculation to main thread)
6/6 Checking commit 7c3806f92697 (migration/dirtyrate: implement dirty-ring dirtyrate calculation)
ERROR: trailing whitespace
#88: FILE: migration/dirtyrate.c:93:
+ $

WARNING: line over 80 characters
#94: FILE: migration/dirtyrate.c:99:
+            /* set sample_pages with 0 to indicate page sampling isn't enabled */

ERROR: trailing whitespace
#106: FILE: migration/dirtyrate.c:111:
+   $

ERROR: trailing whitespace
#325: FILE: migration/dirtyrate.c:658:
+    qapi_free_DirtyRateVcpuList(info->vcpu_dirty_rate); $

total: 3 errors, 1 warnings, 350 lines checked

Patch 6/6 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/cover.1623934182.git.huangy81@chinatelecom.cn/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

      parent reply	other threads:[~2021-06-17 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 13:01 [PATCH v5 0/6] support dirtyrate at the granualrity of vcpu huangy81
2021-06-17 13:01 ` [PATCH v5 1/6] memory: rename global_dirty_log to global_dirty_tracking huangy81
2021-06-17 13:01 ` [PATCH v5 2/6] memory: make global_dirty_tracking a bitmask huangy81
2021-06-17 13:01 ` [PATCH v5 3/6] migration/dirtyrate: introduce struct and adjust DirtyRateStat huangy81
2021-06-17 13:01 ` [PATCH v5 4/6] migration/dirtyrate: adjust order of registering thread huangy81
2021-06-17 13:01 ` [PATCH v5 5/6] migration/dirtyrate: move init step of calculation to main thread huangy81
2021-06-17 13:01 ` [PATCH v5 6/6] migration/dirtyrate: implement dirty-ring dirtyrate calculation huangy81
2021-06-17 13:27 ` no-reply [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=162393646568.30552.12017277222021052187@7c66fb7bc3ab \
    --to=no-reply@patchew.org \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=huangy81@chinatelecom.cn \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=zhengchuan@huawei.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 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.