From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, armbru@redhat.com, mreitz@redhat.com,
marcandre.lureau@gmail.com, pbonzini@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v9 00/11] Provide a QOM-based authorization API
Date: Mon, 15 Aug 2016 14:07:08 +0100 [thread overview]
Message-ID: <20160815130708.GG13261@redhat.com> (raw)
In-Reply-To: <20160815130353.482798.96081@ex-std-node742.prod.rhcloud.com>
On Mon, Aug 15, 2016 at 06:04:02AM -0700, no-reply@ec2-52-6-146-230.compute-1.amazonaws.com wrote:
> Hi,
>
> Your series seems to have some coding style problems. See output below for
> more information:
>
> Message-id: 1471265145-12558-1-git-send-email-berrange@redhat.com
> Subject: [Qemu-devel] [PATCH v9 00/11] Provide a QOM-based authorization API
> Type: series
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
>
> BASE=base
> n=1
> total=$(git log --oneline $BASE.. | wc -l)
> failed=0
>
> commits="$(git log --format=%H --reverse $BASE..)"
> for c in $commits; do
> echo "Checking PATCH $n/$total: $(git show --no-patch --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
> * [new tag] patchew/1471265145-12558-1-git-send-email-berrange@redhat.com -> patchew/1471265145-12558-1-git-send-email-berrange@redhat.com
> Switched to a new branch 'test'
> 3a1d870 qmp: add support for mixed typed input visitor
> 01a6fe2 util: add QAuthZPAM object type for authorizing using PAM
> b0380fb acl: delete existing ACL implementation
> 3de7df2 util: add QAuthZSimple object type for a simple access control list
> 6e54576 util: add QAuthZ object as an authorization base class
> a128fba qom: support arbitrary non-scalar properties with -object
> 33a535d qapi: add a QmpInputVisitor that does string conversion
> dcbcfba qapi: rename QmpOutputVisitor to QObjectOutputVisitor
> 2b2fc3a qapi: rename QmpInputVisitor to QObjectInputVisitor
> f2552c3 option: make parse_option_bool/number non-static
> 4f7ac55 qdict: implement a qdict_crumple method for un-flattening a dict
>
> === OUTPUT BEGIN ===
> Checking PATCH 1/11: qdict: implement a qdict_crumple method for un-flattening a dict...
> Checking PATCH 2/11: option: make parse_option_bool/number non-static...
> Checking PATCH 3/11: qapi: rename QmpInputVisitor to QObjectInputVisitor...
> ERROR: open brace '{' following struct go on the same line
> #572: FILE: qapi/qobject-input-visitor.c:27:
> +typedef struct StackObject
> +{
[snip]
This and all the other errors reported here are all *pre-existing*
problems. It seems this bot does not have git rename detection turned
on so is reporting all these problems in file-renames my patches did.
The bot needs to have something like this added to its $HOME/.gitconfig:
[diff]
renamelimit=1000
renames=True
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-08-15 13:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 12:45 [Qemu-devel] [PATCH v9 00/11] Provide a QOM-based authorization API Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 01/11] qdict: implement a qdict_crumple method for un-flattening a dict Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 02/11] option: make parse_option_bool/number non-static Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 03/11] qapi: rename QmpInputVisitor to QObjectInputVisitor Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 04/11] qapi: rename QmpOutputVisitor to QObjectOutputVisitor Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 05/11] qapi: add a QmpInputVisitor that does string conversion Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 06/11] qom: support arbitrary non-scalar properties with -object Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 07/11] util: add QAuthZ object as an authorization base class Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 08/11] util: add QAuthZSimple object type for a simple access control list Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 09/11] acl: delete existing ACL implementation Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 10/11] util: add QAuthZPAM object type for authorizing using PAM Daniel P. Berrange
2016-08-15 12:45 ` [Qemu-devel] [PATCH v9 11/11] qmp: add support for mixed typed input visitor Daniel P. Berrange
2016-08-15 13:04 ` [Qemu-devel] [PATCH v9 00/11] Provide a QOM-based authorization API no-reply
2016-08-15 13:07 ` Daniel P. Berrange [this message]
2016-08-16 1:33 ` Fam Zheng
2016-08-15 13:05 ` no-reply
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=20160815130708.GG13261@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.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).