From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: chenmin.sun@intel.com
Subject: [dpdk-test-report] |WARNING| pw71347 [PATCH] net/i40e: i40e FDIR update rate optimization
Date: Fri, 12 Jun 2020 11:04:04 +0200 (CEST) [thread overview]
Message-ID: <20200612090404.D771A2BAA@dpdk.org> (raw)
In-Reply-To: <20200612180015.14760-1-chenmin.sun@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/71347
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#121: FILE: drivers/net/i40e/i40e_ethdev.c:1106:
+ alloc = ((pfqf_fdalloc & I40E_PFQF_FDALLOC_FDALLOC_MASK) >> I40E_PFQF_FDALLOC_FDALLOC_SHIFT);
WARNING:LONG_LINE: line over 90 characters
#122: FILE: drivers/net/i40e/i40e_ethdev.c:1107:
+ best = ((pfqf_fdalloc & I40E_PFQF_FDALLOC_FDBEST_MASK) >> I40E_PFQF_FDALLOC_FDBEST_SHIFT);
WARNING:LONG_LINE: line over 90 characters
#372: FILE: drivers/net/i40e/i40e_fdir.c:247:
+ pf->fdir.prg_pkt[i] = (uint8_t *)mz->addr + I40E_FDIR_PKT_LEN * (i % PRG_PKT_CNT);
WARNING:LONG_LINE: line over 90 characters
#882: FILE: drivers/net/i40e/i40e_flow.c:5149:
+ flow = &fdir_info->fdir_flow_bitmap.fdir_flow[pos + i].flow;
WARNING:LONG_LINE_COMMENT: line over 90 characters
#979: FILE: drivers/net/i40e/i40e_flow.c:5288:
+ /* check if the budget will be gained back to guaranteed space */
total: 0 errors, 5 warnings, 0 checks, 928 lines checked
next parent reply other threads:[~2020-06-12 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200612180015.14760-1-chenmin.sun@intel.com>
2020-06-12 9:04 ` checkpatch [this message]
2020-06-12 11:15 ` [dpdk-test-report] |SUCCESS| pw71347 " 0-day Robot
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=20200612090404.D771A2BAA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chenmin.sun@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).