automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Alfredo Cardigliano <cardigliano@ntop.org>
Subject: [dpdk-test-report] |WARNING| pw61002 [PATCH 12/17] net/ionic: net-ionic-add-flow-control-support
Date: Sat, 12 Oct 2019 02:28:39 +0200 (CEST)	[thread overview]
Message-ID: <20191012002839.978541EB91@dpdk.org> (raw)
In-Reply-To: <157084004735.11524.15147383251636783986.stgit@devele>

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

_coding style issues_


ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#93: FILE: drivers/net/ionic/ionic_ethdev.c:286:
+	switch (fc_conf->mode) {
+		case RTE_FC_NONE:
[...]
+		case RTE_FC_FULL:
[...]
+		case RTE_FC_RX_PAUSE:
+		case RTE_FC_TX_PAUSE:

total: 1 errors, 0 warnings, 0 checks, 81 lines checked

           reply	other threads:[~2019-10-12  0:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <157084004735.11524.15147383251636783986.stgit@devele>]

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=20191012002839.978541EB91@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=cardigliano@ntop.org \
    --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).