automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pascal Mazon <pascal.mazon@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw21808 [PATCH] net/tap: support segmented mbufs
Date: Wed, 15 Mar 2017 18:44:14 +0100 (CET)	[thread overview]
Message-ID: <20170315174414.114BF214A@dpdk.org> (raw)
In-Reply-To: <74ac5afc58ae941184f3886c5eeb9fbc8b5d9c9d.1489590563.git.pascal.mazon@6wind.com>

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

_coding style issues_


WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#381: FILE: drivers/net/tap/rte_eth_tap.h:64:
+^Iuint16_t nb_rx_desc;           ^I/* max number of mbufs available */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#382: FILE: drivers/net/tap/rte_eth_tap.h:65:
+^Istruct rte_eth_rxmode *rxmode; ^I/* RX features */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#383: FILE: drivers/net/tap/rte_eth_tap.h:66:
+^Istruct rte_mbuf *pool;         ^I/* mbufs pool for this queue */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#384: FILE: drivers/net/tap/rte_eth_tap.h:67:
+^Istruct iovec (*iovecs)[];      ^I/* descriptors for this queue */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#385: FILE: drivers/net/tap/rte_eth_tap.h:68:
+^Istruct tun_pi pi;              ^I/* packet info for iovecs */$

total: 0 errors, 5 warnings, 0 checks, 335 lines checked

           reply	other threads:[~2017-03-15 17:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <74ac5afc58ae941184f3886c5eeb9fbc8b5d9c9d.1489590563.git.pascal.mazon@6wind.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=20170315174414.114BF214A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=pascal.mazon@6wind.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).