From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Soumyadeep Hore <soumyadeep.hore@intel.com>
Subject: |WARNING| pw140381 [PATCH 25/25] net/cpfl: updating idpf vc queue switch in cpfl
Date: Tue, 28 May 2024 10:20:44 +0200 (CEST) [thread overview]
Message-ID: <20240528082044.5B04312367B@dpdk.org> (raw)
In-Reply-To: <20240528073630.867131-6-soumyadeep.hore@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140381
_coding style issues_
WARNING:LONG_LINE: line length of 119 exceeds 100 columns
#85: FILE: drivers/net/cpfl/cpfl_ethdev.c:1910:
+ ret = idpf_vc_queue_switch(&adapter->ctrl_vport.base, i, false, false, VIRTCHNL2_QUEUE_TYPE_CONFIG_TX);
WARNING:LONG_LINE: line length of 118 exceeds 100 columns
#94: FILE: drivers/net/cpfl/cpfl_ethdev.c:1918:
+ ret = idpf_vc_queue_switch(&adapter->ctrl_vport.base, i, true, false, VIRTCHNL2_QUEUE_TYPE_CONFIG_RX);
WARNING:LONG_LINE: line length of 118 exceeds 100 columns
#103: FILE: drivers/net/cpfl/cpfl_ethdev.c:1946:
+ ret = idpf_vc_queue_switch(&adapter->ctrl_vport.base, i, false, true, VIRTCHNL2_QUEUE_TYPE_CONFIG_TX);
WARNING:LONG_LINE: line length of 117 exceeds 100 columns
#112: FILE: drivers/net/cpfl/cpfl_ethdev.c:1954:
+ ret = idpf_vc_queue_switch(&adapter->ctrl_vport.base, i, true, true, VIRTCHNL2_QUEUE_TYPE_CONFIG_RX);
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#143: FILE: drivers/net/cpfl/cpfl_rxtx.c:1286:
+ err = idpf_vc_queue_switch(vport, rx_queue_id, true, false, VIRTCHNL2_QUEUE_TYPE_RX);
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#152: FILE: drivers/net/cpfl/cpfl_rxtx.c:1334:
+ err = idpf_vc_queue_switch(vport, tx_queue_id, false, false, VIRTCHNL2_QUEUE_TYPE_TX);
total: 0 errors, 6 warnings, 0 checks, 64 lines checked
next prev parent reply other threads:[~2024-05-28 8:20 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528073630.867131-6-soumyadeep.hore@intel.com>
2024-05-28 7:53 ` |SUCCESS| pw140357-140381 " qemudev
2024-05-28 7:58 ` qemudev
2024-05-28 8:20 ` checkpatch [this message]
2024-05-28 9:23 ` |FAILURE| pw140381 " 0-day Robot
2024-05-28 10:00 ` |SUCCESS| pw140357-140381 [PATCH] [25/25] net/cpfl: updating idpf vc dpdklab
2024-05-28 10:00 ` dpdklab
2024-05-28 10:41 ` dpdklab
2024-05-28 10:42 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:49 ` dpdklab
2024-05-28 10:49 ` dpdklab
2024-05-28 10:50 ` dpdklab
2024-05-28 10:50 ` dpdklab
2024-05-28 10:54 ` dpdklab
2024-05-28 10:56 ` dpdklab
2024-05-28 10:57 ` dpdklab
2024-05-28 10:58 ` dpdklab
2024-05-28 10:59 ` dpdklab
2024-05-28 10:59 ` dpdklab
2024-05-28 11:00 ` dpdklab
2024-05-28 11:00 ` dpdklab
2024-05-28 11:02 ` dpdklab
2024-05-28 11:02 ` dpdklab
2024-05-28 11:15 ` dpdklab
2024-05-28 11:36 ` dpdklab
2024-05-28 12:00 ` |FAILURE| " dpdklab
2024-05-28 12:01 ` dpdklab
2024-05-28 12:01 ` dpdklab
2024-05-28 12:07 ` dpdklab
2024-05-28 12:24 ` dpdklab
2024-05-28 12:32 ` |SUCCESS| " dpdklab
2024-05-28 12:32 ` dpdklab
2024-05-28 12:33 ` dpdklab
2024-05-28 12:35 ` dpdklab
2024-05-28 12:36 ` |FAILURE| " dpdklab
2024-05-28 12:37 ` dpdklab
2024-05-28 12:42 ` dpdklab
2024-05-28 12:42 ` dpdklab
2024-05-28 12:44 ` dpdklab
2024-05-28 12:45 ` |SUCCESS| " dpdklab
2024-05-28 12:45 ` dpdklab
2024-05-28 12:46 ` dpdklab
2024-05-28 12:46 ` |FAILURE| " dpdklab
2024-05-28 12:47 ` |SUCCESS| " dpdklab
2024-05-28 12:48 ` dpdklab
2024-05-28 12:49 ` |FAILURE| " dpdklab
2024-05-28 12:49 ` dpdklab
2024-05-28 12:50 ` dpdklab
2024-05-28 12:50 ` dpdklab
2024-05-28 12:51 ` |SUCCESS| " dpdklab
2024-05-28 12:52 ` dpdklab
2024-05-28 12:53 ` dpdklab
2024-05-28 12:54 ` dpdklab
2024-05-28 12:55 ` |FAILURE| " dpdklab
2024-05-28 12:55 ` dpdklab
2024-05-28 12:55 ` |SUCCESS| " dpdklab
2024-05-28 12:56 ` dpdklab
2024-05-28 12:56 ` |FAILURE| " dpdklab
2024-05-28 12:57 ` dpdklab
2024-05-28 12:57 ` |SUCCESS| " dpdklab
2024-05-28 12:57 ` |FAILURE| " dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 12:59 ` |SUCCESS| " dpdklab
2024-05-28 12:59 ` |FAILURE| " dpdklab
2024-05-28 13:00 ` dpdklab
2024-05-28 13:00 ` |SUCCESS| " dpdklab
2024-05-28 13:01 ` dpdklab
2024-05-28 13:02 ` |FAILURE| " dpdklab
2024-05-28 13:02 ` dpdklab
2024-05-28 13:03 ` dpdklab
2024-05-28 13:05 ` |SUCCESS| " dpdklab
2024-05-28 13:06 ` |FAILURE| " dpdklab
2024-05-28 13:07 ` dpdklab
2024-05-28 13:09 ` dpdklab
2024-05-28 13:10 ` |SUCCESS| " dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:20 ` dpdklab
2024-05-28 13:20 ` |FAILURE| " dpdklab
2024-05-28 13:23 ` |SUCCESS| " dpdklab
2024-05-28 13:25 ` dpdklab
2024-05-28 14:17 ` dpdklab
2024-05-28 14:19 ` |FAILURE| " dpdklab
2024-05-28 14:46 ` |SUCCESS| " dpdklab
2024-05-30 2:21 ` dpdklab
2024-05-30 2:21 ` dpdklab
2024-05-30 2:24 ` dpdklab
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=20240528082044.5B04312367B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=soumyadeep.hore@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).