From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Zhichao Zeng <zhichaox.zeng@intel.com>
Subject: |WARNING| pw128645 [PATCH v5 3/3] net/iavf: support Rx timestamp offload on SSE
Date: Wed, 14 Jun 2023 03:45:42 +0200 (CEST) [thread overview]
Message-ID: <20230614014543.040A41208D8@dpdk.org> (raw)
In-Reply-To: <20230614014948.3495063-4-zhichaox.zeng@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/128645
_coding style issues_
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#196: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1022:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 0);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#198: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1024:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 1);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#200: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1026:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 2);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#202: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1028:
+ iavf_timestamp_dynfield_offset, uint32_t *) = _mm_extract_epi32(ts_low, 3);
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#211: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1037:
+ rxq->phc_time = iavf_tstamp_convert_32b_64b(rxq->phc_time, in_timestamp);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#215: 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
#217: 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
#219: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1045:
+ iavf_timestamp_dynfield_offset + 4, uint32_t *) = (uint32_t)(rxq->phc_time >> 32);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#221: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:1047:
+ iavf_timestamp_dynfield_offset + 4, uint32_t *) = (uint32_t)(rxq->phc_time >> 32);
total: 0 errors, 9 warnings, 0 checks, 210 lines checked
next prev parent reply other threads:[~2023-06-14 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230614014948.3495063-4-zhichaox.zeng@intel.com>
2023-06-14 1:33 ` |SUCCESS| pw128643-128645 " qemudev
2023-06-14 1:37 ` qemudev
2023-06-14 1:45 ` checkpatch [this message]
2023-06-14 2:59 ` |SUCCESS| pw128645 " 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=20230614014543.040A41208D8@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).