automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Július Milan" <jmilan.dev@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw65507 [PATCH] net/memif: add dev_link info
Date: Tue,  4 Feb 2020 09:48:08 +0100 (CET)	[thread overview]
Message-ID: <20200204084808.80D9C1C05C@dpdk.org> (raw)
In-Reply-To: <CAP=P++AXsmkgaMKZ_EGSgWkDTqg9a+ueJm=D04cM54AxmXbz9A@mail.gmail.com>

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

_coding style issues_


WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: drivers/net/memif/rte_eth_memif.c:56:
+    .link_speed = ETH_SPEED_NUM_10G,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#89: FILE: drivers/net/memif/rte_eth_memif.c:57:
+    .link_duplex = ETH_LINK_FULL_DUPLEX,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#90: FILE: drivers/net/memif/rte_eth_memif.c:58:
+    .link_status = ETH_LINK_DOWN,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#91: FILE: drivers/net/memif/rte_eth_memif.c:59:
+    .link_autoneg = ETH_LINK_AUTONEG$

ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#98: FILE: drivers/net/memif/rte_eth_memif.c:1494:
memif_role_t role,

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#102: FILE: drivers/net/memif/rte_eth_memif.c:1498:
+    data->dev_link = pmd_link;$

total: 1 errors, 5 warnings, 0 checks, 20 lines checked

           reply	other threads:[~2020-02-04  8:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAP=P++AXsmkgaMKZ_EGSgWkDTqg9a+ueJm=D04cM54AxmXbz9A@mail.gmail.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=20200204084808.80D9C1C05C@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=jmilan.dev@gmail.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).