automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw55591 [PATCH v4 1/2] lib/ipsec: add support for header construction
Date: Fri, 28 Jun 2019 14:46:55 +0200 (CEST)	[thread overview]
Message-ID: <20190628124655.0B1DB559A@dpdk.org> (raw)
In-Reply-To: <20190628123926.15762-2-roy.fan.zhang@intel.com>

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

_coding style issues_


ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#107: FILE: lib/librte_ipsec/iph.h:118:
+#define SET_IPV6_TC(vtc_flow, tc)					\
+	vtc_flow = rte_cpu_to_be_32(tc << RTE_IPV6_HDR_TC_SHIFT) |	\
+		(vtc_flow & (~rte_cpu_to_be_32(IPV6_TOS_MASK)))		\
+

total: 1 errors, 0 warnings, 293 lines checked

           reply	other threads:[~2019-06-28 12:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190628123926.15762-2-roy.fan.zhang@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=20190628124655.0B1DB559A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=roy.fan.zhang@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).