All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: peterx@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com,
	dgilbert@redhat.com, stefanha@redhat.com,
	marcandre.lureau@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 0/4] monitor: let Monitor be thread safe
Date: Wed, 23 May 2018 21:46:11 -0700 (PDT)	[thread overview]
Message-ID: <152713717041.150.6588831627203825308@d39dc562802a> (raw)
In-Reply-To: <20180524043952.11245-1-peterx@redhat.com>

Hi,

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

Type: series
Message-id: 20180524043952.11245-1-peterx@redhat.com
Subject: [Qemu-devel] [PATCH v7 0/4] monitor: let Monitor be thread safe

=== 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
 t [tag update]            patchew/20180522035629.30428-1-peterx@redhat.com -> patchew/20180522035629.30428-1-peterx@redhat.com
 * [new tag]               patchew/20180524043952.11245-1-peterx@redhat.com -> patchew/20180524043952.11245-1-peterx@redhat.com
Switched to a new branch 'test'
dadcba2375 monitor: add lock to protect mon_fdsets
eda66671b9 monitor: more comments on lock-free fleids/funcs
b7d356e160 monitor: protect mon->fds with mon_lock
35eadfaff2 monitor: rename out_lock to mon_lock

=== OUTPUT BEGIN ===
Checking PATCH 1/4: monitor: rename out_lock to mon_lock...
Checking PATCH 2/4: monitor: protect mon->fds with mon_lock...
Checking PATCH 3/4: monitor: more comments on lock-free fleids/funcs...
ERROR: do not use C99 // comments
#28: FILE: monitor.c:218:
+    // other members that aren't shared

total: 1 errors, 0 warnings, 31 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 4/4: monitor: add lock to protect mon_fdsets...
=== 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

      parent reply	other threads:[~2018-05-24  4:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  4:39 [Qemu-devel] [PATCH v7 0/4] monitor: let Monitor be thread safe Peter Xu
2018-05-24  4:39 ` [Qemu-devel] [PATCH v7 1/4] monitor: rename out_lock to mon_lock Peter Xu
2018-05-24  8:29   ` Markus Armbruster
2018-05-24  8:45     ` Peter Xu
2018-05-24 11:14       ` Markus Armbruster
2018-05-24  4:39 ` [Qemu-devel] [PATCH v7 2/4] monitor: protect mon->fds with mon_lock Peter Xu
2018-05-24  4:39 ` [Qemu-devel] [PATCH v7 3/4] monitor: more comments on lock-free fleids/funcs Peter Xu
2018-05-24  8:08   ` Stefan Hajnoczi
2018-05-24  8:49     ` Peter Xu
2018-05-24  8:41   ` Markus Armbruster
2018-05-24  8:48     ` Peter Xu
2018-05-24 11:16       ` Markus Armbruster
2018-05-28  6:28         ` Peter Xu
2018-05-24  4:39 ` [Qemu-devel] [PATCH v7 4/4] monitor: add lock to protect mon_fdsets Peter Xu
2018-05-24  9:03   ` Markus Armbruster
2018-05-28  7:06     ` Peter Xu
2018-05-28 15:19       ` Markus Armbruster
2018-05-29  5:51         ` Peter Xu
2018-05-24  9:28   ` Stefan Hajnoczi
2018-05-25  3:30     ` Peter Xu
2018-05-25  9:01       ` Stefan Hajnoczi
2018-05-28  6:29         ` Peter Xu
2018-05-24  4:46 ` 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=152713717041.150.6588831627203825308@d39dc562802a \
    --to=no-reply@patchew.org \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=peterx@redhat.com \
    --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 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.