From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138141 [RFC v3] tap: do not duplicate fd's
Date: Sat, 9 Mar 2024 19:17:34 +0100 (CET) [thread overview]
Message-ID: <20240309181734.521D81223EF@dpdk.org> (raw)
In-Reply-To: <20240309181554.289317-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138141
_coding style issues_
WARNING:TYPO_SPELLING: 'devic' may be misspelled - perhaps 'device'?
#84:
The TAP devic can use the same file descriptor for both rx and tx queues.
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#85:
This allows up to 8 queues (versus 4) and reduces some resource consumption.
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#529: FILE: drivers/net/tap/tap_intr.c:77:
+ RTE_INTR_VEC_RXTX_OFFSET + RTE_MAX_RXTX_INTR_VEC_ID))
total: 0 errors, 3 warnings, 0 checks, 397 lines checked
next prev parent reply other threads:[~2024-03-09 18:17 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240309181554.289317-1-stephen@networkplumber.org>
2024-03-09 17:53 ` |SUCCESS| " qemudev
2024-03-09 17:57 ` qemudev
2024-03-09 18:17 ` checkpatch [this message]
2024-03-09 19:00 ` |SUCCESS| pw138141 [PATCH] [RFC,v3] " dpdklab
2024-03-09 19:01 ` dpdklab
2024-03-09 19:01 ` dpdklab
2024-03-09 19:01 ` dpdklab
2024-03-09 19:02 ` dpdklab
2024-03-09 19:02 ` dpdklab
2024-03-09 19:02 ` dpdklab
2024-03-09 19:02 ` dpdklab
2024-03-09 19:02 ` dpdklab
2024-03-09 19:02 ` dpdklab
2024-03-09 19:03 ` |SUCCESS| pw138141 [RFC v3] " 0-day Robot
2024-03-09 19:03 ` |SUCCESS| pw138141 [PATCH] [RFC,v3] " dpdklab
2024-03-09 19:03 ` dpdklab
2024-03-09 19:03 ` dpdklab
2024-03-09 19:04 ` dpdklab
2024-03-09 19:04 ` dpdklab
2024-03-09 19:04 ` dpdklab
2024-03-09 19:04 ` dpdklab
2024-03-09 19:04 ` dpdklab
2024-03-09 19:05 ` dpdklab
2024-03-09 19:05 ` dpdklab
2024-03-09 19:06 ` dpdklab
2024-03-09 19:06 ` dpdklab
2024-03-09 19:06 ` dpdklab
2024-03-09 19:06 ` dpdklab
2024-03-09 19:06 ` dpdklab
2024-03-09 19:07 ` dpdklab
2024-03-09 19:07 ` dpdklab
2024-03-09 19:07 ` dpdklab
2024-03-09 19:07 ` dpdklab
2024-03-09 19:07 ` dpdklab
2024-03-09 19:07 ` dpdklab
2024-03-09 19:08 ` dpdklab
2024-03-09 19:08 ` dpdklab
2024-03-09 19:08 ` dpdklab
2024-03-09 19:08 ` dpdklab
2024-03-09 19:08 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:09 ` dpdklab
2024-03-09 19:10 ` dpdklab
2024-03-09 19:10 ` dpdklab
2024-03-09 19:10 ` dpdklab
2024-03-09 19:10 ` dpdklab
2024-03-09 19:11 ` dpdklab
2024-03-09 19:11 ` dpdklab
2024-03-09 19:11 ` dpdklab
2024-03-09 19:11 ` dpdklab
2024-03-09 19:11 ` dpdklab
2024-03-09 19:12 ` dpdklab
2024-03-09 19:12 ` dpdklab
2024-03-09 19:12 ` dpdklab
2024-03-09 19:13 ` dpdklab
2024-03-09 19:14 ` dpdklab
2024-03-09 19:14 ` dpdklab
2024-03-09 19:21 ` dpdklab
2024-03-09 19:22 ` dpdklab
2024-03-09 19:28 ` dpdklab
2024-03-09 19:33 ` dpdklab
2024-03-09 19:34 ` dpdklab
2024-03-09 20:14 ` dpdklab
2024-03-14 2:20 ` dpdklab
2024-03-14 2:56 ` 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=20240309181734.521D81223EF@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).