automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Hanoch Haim \(hhaim\)" <hhaim@cisco.com>
Subject: [dpdk-test-report] |WARNING| pw31379 [PATCH v3] mbuf: cleanup rte_pktmbuf_lastseg() fix atomic usage
Date: Wed, 15 Nov 2017 10:15:20 +0100 (CET)	[thread overview]
Message-ID: <20171115091520.4D6E01B1EE@dpdk.org> (raw)
In-Reply-To: <20171115091413.27119-1-hhaim@cisco.com>

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

_coding style issues_


ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#24: FILE: lib/librte_mbuf/rte_mbuf.h:1158:
	__rte_mbuf_sanity_check(m, 1);

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (0, 16)
#42: FILE: lib/librte_mbuf/rte_mbuf.h:1332:
	if (rte_mbuf_refcnt_update(md, -1) == 0) {
+		rte_pktmbuf_reset_before_free(md);

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 8)
#63: FILE: lib/librte_mbuf/rte_mbuf.h:1365:
+	} else if (rte_mbuf_refcnt_update(m, -1) == 0) {
[...]
		if (RTE_MBUF_INDIRECT(m))

total: 1 errors, 2 warnings, 52 lines checked

           reply	other threads:[~2017-11-15  9:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171115091413.27119-1-hhaim@cisco.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=20171115091520.4D6E01B1EE@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=hhaim@cisco.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).