From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
Subject: [dpdk-test-report] |WARNING| pw22267 [PATCH v3 61/61] net/qede: add LRO/TSO offloads support
Date: Fri, 24 Mar 2017 10:43:39 +0100 (CET) [thread overview]
Message-ID: <20170324094339.3C7EFCF9E@dpdk.org> (raw)
In-Reply-To: <1490340531-11403-62-git-send-email-rasesh.mody@cavium.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/22267
_coding style issues_
WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'cqe_start_tpa->len_on_first_bd'
#450: FILE: drivers/net/qede/qede_rxtx.c:1045:
+ rte_le_to_cpu_16(cqe_start_tpa->
+ len_on_first_bd),
WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'cqe_start_tpa->ext_bd_len_list[0]'
#453: FILE: drivers/net/qede/qede_rxtx.c:1048:
+ rte_le_to_cpu_16(cqe_start_tpa->
+ ext_bd_len_list[0]),
WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'rxq->tpa_info[cqe->fast_path_tpa_end.tpa_agg_index].mbuf'
#465: FILE: drivers/net/qede/qede_rxtx.c:1060:
+ rx_mb = rxq->
+ tpa_info[cqe->fast_path_tpa_end.tpa_agg_index].mbuf;
WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'cqe_start_tpa->pars_flags.flags'
#512: FILE: drivers/net/qede/qede_rxtx.c:1087:
+ parse_flag = rte_le_to_cpu_16(cqe_start_tpa->
+ pars_flags.flags);
WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'cqe_start_tpa->tunnel_pars_flags.flags'
#541: FILE: drivers/net/qede/qede_rxtx.c:1108:
+ tunn_parse_flag = cqe_start_tpa->
+ tunnel_pars_flags.flags;
WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'fp_cqe->tunnel_pars_flags.flags'
#544: FILE: drivers/net/qede/qede_rxtx.c:1111:
+ tunn_parse_flag = fp_cqe->
+ tunnel_pars_flags.flags;
total: 0 errors, 6 warnings, 0 checks, 1186 lines checked
parent reply other threads:[~2017-03-24 9:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1490340531-11403-62-git-send-email-rasesh.mody@cavium.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=20170324094339.3C7EFCF9E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=Rasesh.Mody@cavium.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).