From: no-reply@patchew.org
To: lvivier@redhat.com
Cc: famz@redhat.com, david@gibson.dropbear.id.au, thuth@redhat.com,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org, groug@kaod.org
Subject: Re: [Qemu-devel] [PATCH v3 0/2] tests: add RTAS protocol
Date: Tue, 6 Sep 2016 04:26:03 -0700 (PDT) [thread overview]
Message-ID: <20160906112600.76034.82597@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1473160625-6377-1-git-send-email-lvivier@redhat.com>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v3 0/2] tests: add RTAS protocol
Type: series
Message-id: 1473160625-6377-1-git-send-email-lvivier@redhat.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline $BASE.. | wc -l)
failed=0
# Useful git options
git config --local diff.renamelimit 0
git config --local diff.renames True
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/1473160625-6377-1-git-send-email-lvivier@redhat.com -> patchew/1473160625-6377-1-git-send-email-lvivier@redhat.com
Switched to a new branch 'test'
2acbc73 tests: add RTAS command in the protocol
ba5d51c tests: make pc_alloc_init/init_flags/uninit generic
=== OUTPUT BEGIN ===
Checking PATCH 1/2: tests: make pc_alloc_init/init_flags/uninit generic...
Checking PATCH 2/2: tests: add RTAS command in the protocol...
ERROR: consider using qemu_strtol in preference to strtol
#90: FILE: qtest.c:539:
+ nargs = strtol(words[2], NULL, 0);
ERROR: consider using qemu_strtoll in preference to strtoll
#91: FILE: qtest.c:540:
+ args = strtoll(words[3], NULL, 0);
ERROR: consider using qemu_strtol in preference to strtol
#92: FILE: qtest.c:541:
+ nret = strtol(words[4], NULL, 0);
ERROR: consider using qemu_strtoll in preference to strtoll
#93: FILE: qtest.c:542:
+ ret = strtoll(words[5], NULL, 0);
total: 4 errors, 0 warnings, 252 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.
=== OUTPUT END ===
Test command exited with code: 1
---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@freelists.org
prev parent reply other threads:[~2016-09-06 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 11:17 [Qemu-devel] [PATCH v3 0/2] tests: add RTAS protocol Laurent Vivier
2016-09-06 11:17 ` [Qemu-devel] [PATCH v3 1/2] tests: make pc_alloc_init/init_flags/uninit generic Laurent Vivier
2016-09-06 11:17 ` [Qemu-devel] [PATCH v3 2/2] tests: add RTAS command in the protocol Laurent Vivier
2016-09-06 11:26 ` 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=20160906112600.76034.82597@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=david@gibson.dropbear.id.au \
--cc=famz@redhat.com \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@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 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).