From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com
Subject: |WARNING| pw146200 [Patch v5] net/netvsc: fix number Tx queues > Rx queues
Date: Thu, 17 Oct 2024 21:21:33 +0200 (CEST) [thread overview]
Message-ID: <20241017192133.A8F761206AA@dpdk.org> (raw)
In-Reply-To: <1729192829-30211-1-git-send-email-longli@linuxonhyperv.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/146200
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#120: FILE: drivers/net/netvsc/hn_rxtx.c:225:
+static void
+hn_rx_queue_free_common(struct hn_rx_queue *rxq) {
total: 1 errors, 0 warnings, 0 checks, 145 lines checked
next prev parent reply other threads:[~2024-10-17 19:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1729192829-30211-1-git-send-email-longli@linuxonhyperv.com>
2024-10-17 18:57 ` |SUCCESS| " qemudev
2024-10-17 19:01 ` qemudev
2024-10-17 19:21 ` checkpatch [this message]
2024-10-17 21:02 ` 0-day Robot
2024-10-18 13:11 ` |SUCCESS| pw146200 [PATCH] [v5] net/netvsc: fix number Tx queues > R dpdklab
2024-10-18 19:40 ` dpdklab
2024-10-18 20:04 ` dpdklab
2024-10-19 1:40 ` dpdklab
2024-10-19 2:17 ` dpdklab
2024-10-19 6:48 ` |PENDING| " dpdklab
2024-10-19 6:53 ` |SUCCESS| " dpdklab
2024-10-19 7:04 ` |PENDING| " dpdklab
2024-10-19 7:33 ` dpdklab
2024-10-19 8:03 ` |FAILURE| " dpdklab
2024-10-19 8:05 ` dpdklab
2024-10-19 8:06 ` dpdklab
2024-10-19 10:19 ` |SUCCESS| " dpdklab
2024-10-19 10:21 ` dpdklab
2024-10-19 11:24 ` |FAILURE| " dpdklab
2024-10-19 13:28 ` |SUCCESS| " dpdklab
2024-10-19 13:38 ` dpdklab
2024-10-21 1:54 ` |FAILURE| " dpdklab
2024-10-22 4:45 ` |SUCCESS| " dpdklab
2024-10-23 8:51 ` dpdklab
2024-10-23 8:52 ` 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=20241017192133.A8F761206AA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=longli@linuxonhyperv.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).