From: no-reply@patchew.org
To: kernellwp@gmail.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org,
pbonzini@redhat.com, mst@redhat.com, ehabkost@redhat.com,
wanpeng.li@hotmail.com, rkrcmar@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pc: apic: fix touch LAPIC when irqchip is split
Date: Tue, 13 Sep 2016 20:21:43 -0700 (PDT) [thread overview]
Message-ID: <20160914032140.19908.55883@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1473822299-6302-1-git-send-email-wanpeng.li@hotmail.com>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1473822299-6302-1-git-send-email-wanpeng.li@hotmail.com
Subject: [Qemu-devel] [PATCH] pc: apic: fix touch LAPIC when irqchip is split
=== 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
Switched to a new branch 'test'
9bcacc6 pc: apic: fix touch LAPIC when irqchip is split
=== OUTPUT BEGIN ===
Checking PATCH 1/1: pc: apic: fix touch LAPIC when irqchip is split...
ERROR: suspect code indent for conditional statements (4, 9)
#90: FILE: hw/i386/pc.c:164:
+ if (!kvm_irqchip_in_kernel()) {
+ intno = apic_get_interrupt(cpu->apic_state);
ERROR: suspect code indent for conditional statements (9, 13)
#92: FILE: hw/i386/pc.c:166:
+ if (intno >= 0) {
+ return intno;
ERROR: suspect code indent for conditional statements (9, 13)
#96: FILE: hw/i386/pc.c:170:
+ if (!apic_accept_pic_intr(cpu->apic_state)) {
+ return -1;
total: 3 errors, 0 warnings, 30 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-09-14 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 3:04 [PATCH] pc: apic: fix touch LAPIC when irqchip is split Wanpeng Li
2016-09-14 3:21 ` no-reply [this message]
2016-09-14 3:40 ` [Qemu-devel] " Fam Zheng
2016-09-14 3:47 ` Wanpeng Li
2016-09-14 14:02 ` Radim Krčmář
2016-09-14 14:03 ` Radim Krčmář
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=20160914032140.19908.55883@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.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