From: no-reply@patchew.org
To: lersek@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, peter.maydell@linaro.org,
mst@redhat.com, zhaoshenglong@huawei.com,
alistair.francis@xilinx.com, michael@walle.cc,
qemu-arm@nongnu.org, pbonzini@redhat.com, imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.8 0/2] loader fixes
Date: Tue, 29 Nov 2016 05:37:02 -0800 (PST) [thread overview]
Message-ID: <148042662061.139.8078035742561370423@5b492b8a941d> (raw)
In-Reply-To: <20161128195701.24912-1-lersek@redhat.com>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH for-2.8 0/2] loader fixes
Type: series
Message-id: 20161128195701.24912-1-lersek@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 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
Switched to a new branch 'test'
a700709 loader: fix undefined behavior in rom_order_compare()
54ae01b loader: fix handling of custom address spaces when adding ROM blobs
=== OUTPUT BEGIN ===
Checking PATCH 1/2: loader: fix handling of custom address spaces when adding ROM blobs...
Checking PATCH 2/2: loader: fix undefined behavior in rom_order_compare()...
ERROR: "(foo*)" should be "(foo *)"
#69: FILE: hw/core/loader.c:821:
+ return ((uintptr_t)(void*)rom->as > (uintptr_t)(void*)item->as) ||
total: 1 errors, 0 warnings, 8 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
next prev parent reply other threads:[~2016-11-29 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 19:56 [Qemu-devel] [PATCH for-2.8 0/2] loader fixes Laszlo Ersek
2016-11-28 19:57 ` [Qemu-devel] [PATCH for-2.8 1/2] loader: fix handling of custom address spaces when adding ROM blobs Laszlo Ersek
2016-11-28 23:07 ` Alistair Francis
2016-11-29 16:31 ` Michael S. Tsirkin
2016-11-28 19:57 ` [Qemu-devel] [PATCH for-2.8 2/2] loader: fix undefined behavior in rom_order_compare() Laszlo Ersek
2016-11-28 23:13 ` Alistair Francis
2016-11-29 16:29 ` Michael S. Tsirkin
2016-11-29 18:40 ` Laszlo Ersek
2016-11-29 13:37 ` no-reply [this message]
2016-11-29 16:27 ` [Qemu-devel] [PATCH for-2.8 0/2] loader fixes Michael S. Tsirkin
2016-11-29 18:41 ` Laszlo Ersek
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=148042662061.139.8078035742561370423@5b492b8a941d \
--to=no-reply@patchew.org \
--cc=alistair.francis@xilinx.com \
--cc=famz@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=michael@walle.cc \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhaoshenglong@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 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).