From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Zhichao Zeng <zhichaox.zeng@intel.com>
Subject: |WARNING| pw125953 [PATCH v2 3/3] net/iavf: support Rx timestamp offload on SSE
Date: Wed, 12 Apr 2023 08:46:52 +0200 (CEST) [thread overview]
Message-ID: <20230412064652.DA57E121EF4@dpdk.org> (raw)
In-Reply-To: <20230412065026.3353168-1-zhichaox.zeng@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/125953
_coding style issues_
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#173: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1020:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 0);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#175: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1022:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 1);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#177: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1024:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 2);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#179: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1026:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 3);
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#188: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1035:
+ rxq->phc_time = iavf_tstamp_convert_32b_64b(rxq->phc_time, in_timestamp);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#192: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1039:
+ iavf_timestamp_dynfield_offset + 4, uint32_t *) = (uint32_t)(rxq->phc_time >> 32);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#194: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1041:
+ iavf_timestamp_dynfield_offset + 4, uint32_t *) = (uint32_t)(rxq->phc_time >> 32);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#196: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1043:
+ iavf_timestamp_dynfield_offset + 4, uint32_t *) = (uint32_t)(rxq->phc_time >> 32);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#198: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1045:
+ iavf_timestamp_dynfield_offset + 4, uint32_t *) = (uint32_t)(rxq->phc_time >> 32);
total: 0 errors, 9 warnings, 0 checks, 195 lines checked
next prev parent reply other threads:[~2023-04-12 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230412065026.3353168-1-zhichaox.zeng@intel.com>
2023-04-12 6:37 ` |SUCCESS| pw125951-125953 " qemudev
2023-04-12 6:41 ` qemudev
2023-04-12 6:46 ` checkpatch [this message]
2023-04-12 7:38 ` |SUCCESS| pw125953 " 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=20230412064652.DA57E121EF4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=zhichaox.zeng@intel.com \
/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).