From: no-reply@patchew.org
To: he.chen@linux.intel.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, drjones@redhat.com,
ehabkost@redhat.com, mst@redhat.com, armbru@redhat.com,
pbonzini@redhat.com, imammedo@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4] Allow setting NUMA distance for different NUMA nodes
Date: Sun, 2 Apr 2017 08:42:11 -0700 (PDT) [thread overview]
Message-ID: <149114773096.14301.8467287626519704750@6c512846dbc7> (raw)
In-Reply-To: <1491042326-24335-1-git-send-email-he.chen@linux.intel.com>
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1491042326-24335-1-git-send-email-he.chen@linux.intel.com
Subject: [Qemu-devel] [PATCH v4] Allow setting NUMA distance for different NUMA nodes
=== 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'
78dd9f1 Allow setting NUMA distance for different NUMA nodes
=== OUTPUT BEGIN ===
Checking PATCH 1/1: Allow setting NUMA distance for different NUMA nodes...
WARNING: line over 80 characters
#173: FILE: numa.c:215:
+static void numa_distance_parse(NumaDistOptions *dist, QemuOpts *opts, Error **errp)
ERROR: braces {} are necessary for all arms of this statement
#234: FILE: numa.c:344:
+ if (numa_info[src].present &&
[...]
ERROR: braces {} are necessary for all arms of this statement
#240: FILE: numa.c:350:
+ if (!have_distance)
[...]
total: 2 errors, 1 warnings, 236 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:[~2017-04-02 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 10:25 [Qemu-devel] [PATCH v4] Allow setting NUMA distance for different NUMA nodes He Chen
2017-04-02 15:42 ` no-reply [this message]
2017-04-03 8:38 ` Andrew Jones
2017-04-03 18:58 ` Eric Blake
2017-04-05 10:17 ` He Chen
2017-04-05 10:03 ` He Chen
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=149114773096.14301.8467287626519704750@6c512846dbc7 \
--to=no-reply@patchew.org \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=he.chen@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.