automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Hunt <david.hunt@intel.com>
Subject: [dpdk-test-report] |WARNING| pw29165 [PATCH v2 5/8] examples/vm_power_mgr: add policy to channels
Date: Mon, 25 Sep 2017 14:39:22 +0200 (CEST)	[thread overview]
Message-ID: <20170925123922.C2BFF1B1B4@dpdk.org> (raw)
In-Reply-To: <1506342429-199695-6-git-send-email-david.hunt@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/29165

_coding style issues_


ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#87: FILE: examples/vm_power_manager/channel_monitor.c:98:
+static void
+core_share_status(int pNo) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#109: FILE: examples/vm_power_manager/channel_monitor.c:120:
+static void
+get_pcpu_to_control(struct policy *pol) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#131: FILE: examples/vm_power_manager/channel_monitor.c:142:
+static int
+get_pfid(struct policy *pol) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#160: FILE: examples/vm_power_manager/channel_monitor.c:171:
+static int
+update_policy(struct channel_packet *pkt) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#199: FILE: examples/vm_power_manager/channel_monitor.c:210:
+static uint64_t
+get_pkt_diff(struct policy *pol) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#233: FILE: examples/vm_power_manager/channel_monitor.c:244:
+static void
+apply_traffic_profile(struct policy *pol) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#265: FILE: examples/vm_power_manager/channel_monitor.c:276:
+static void
+apply_time_profile(struct policy *pol) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#316: FILE: examples/vm_power_manager/channel_monitor.c:327:
+static void
+apply_workload_profile(struct policy *pol) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#342: FILE: examples/vm_power_manager/channel_monitor.c:353:
+static void
+apply_policy(struct policy *pol) {

total: 9 errors, 0 warnings, 414 lines checked

           reply	other threads:[~2017-09-25 12:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1506342429-199695-6-git-send-email-david.hunt@intel.com>]

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=20170925123922.C2BFF1B1B4@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=david.hunt@intel.com \
    --cc=test-report@dpdk.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).