From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "BillXiang" <xiangwencheng@dayudpu.com>
Subject: |WARNING| pw142057 [PATCH] vfio: combine container_create and group_bind
Date: Wed, 3 Jul 2024 10:22:04 +0200 (CEST) [thread overview]
Message-ID: <20240703082204.883B3128144@dpdk.org> (raw)
In-Reply-To: <20240703054124.89490-1-xiangwencheng@dayudpu.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/142057
_coding style issues_
ERROR: symbol rte_vfio_get_fd is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
next prev parent reply other threads:[~2024-07-03 8:22 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240703054124.89490-1-xiangwencheng@dayudpu.com>
2024-07-03 8:05 ` |SUCCESS| " qemudev
2024-07-03 8:10 ` qemudev
2024-07-03 8:22 ` checkpatch [this message]
2024-07-03 9:24 ` |SUCCESS| pw142057 [PATCH] vfio: combine container_create and group_ dpdklab
2024-07-03 9:24 ` |SUCCESS| pw142057 [PATCH] vfio: combine container_create and group_bind 0-day Robot
2024-07-03 9:25 ` |SUCCESS| pw142057 [PATCH] vfio: combine container_create and group_ dpdklab
2024-07-03 9:25 ` dpdklab
2024-07-03 9:26 ` dpdklab
2024-07-03 9:38 ` dpdklab
2024-07-03 9:39 ` dpdklab
2024-07-03 9:44 ` dpdklab
2024-07-03 9:49 ` dpdklab
2024-07-03 9:53 ` |PENDING| " dpdklab
2024-07-03 9:57 ` dpdklab
2024-07-03 9:58 ` dpdklab
2024-07-03 9:58 ` dpdklab
2024-07-03 9:59 ` dpdklab
2024-07-03 10:00 ` |SUCCESS| " dpdklab
2024-07-03 10:00 ` |PENDING| " dpdklab
2024-07-03 10:01 ` dpdklab
2024-07-03 10:02 ` dpdklab
2024-07-03 10:03 ` dpdklab
2024-07-03 10:04 ` dpdklab
2024-07-03 10:04 ` dpdklab
2024-07-03 10:08 ` dpdklab
2024-07-03 10:15 ` dpdklab
2024-07-03 10:22 ` dpdklab
2024-07-03 10:27 ` |SUCCESS| " dpdklab
2024-07-03 10:30 ` dpdklab
2024-07-03 11:25 ` |FAILURE| " dpdklab
2024-07-03 11:26 ` dpdklab
2024-07-03 11:29 ` dpdklab
2024-07-03 11:30 ` dpdklab
2024-07-03 11:31 ` dpdklab
2024-07-03 11:33 ` |PENDING| " dpdklab
2024-07-03 11:36 ` dpdklab
2024-07-03 11:38 ` dpdklab
2024-07-03 11:40 ` dpdklab
2024-07-03 11:42 ` dpdklab
2024-07-03 11:43 ` dpdklab
2024-07-03 11:44 ` dpdklab
2024-07-03 11:47 ` dpdklab
2024-07-03 11:48 ` dpdklab
2024-07-03 11:50 ` dpdklab
2024-07-03 11:53 ` dpdklab
2024-07-03 11:56 ` dpdklab
2024-07-03 11:57 ` dpdklab
2024-07-03 11:57 ` dpdklab
2024-07-03 11:58 ` dpdklab
2024-07-03 12:00 ` dpdklab
2024-07-03 12:01 ` |SUCCESS| " dpdklab
2024-07-03 12:02 ` dpdklab
2024-07-03 12:39 ` |PENDING| " dpdklab
2024-07-03 12:41 ` dpdklab
2024-07-03 12:43 ` dpdklab
2024-07-03 12:48 ` dpdklab
2024-07-03 12:50 ` dpdklab
2024-07-03 12:51 ` dpdklab
2024-07-03 12:51 ` |FAILURE| " dpdklab
2024-07-03 12:51 ` dpdklab
2024-07-03 12:52 ` dpdklab
2024-07-03 12:55 ` dpdklab
2024-07-03 12:58 ` |PENDING| " dpdklab
2024-07-03 12:59 ` dpdklab
2024-07-03 13:03 ` dpdklab
2024-07-03 13:05 ` |FAILURE| " dpdklab
2024-07-03 13:05 ` dpdklab
2024-07-03 13:06 ` dpdklab
2024-07-03 13:06 ` |PENDING| " dpdklab
2024-07-03 13:07 ` |FAILURE| " dpdklab
2024-07-03 13:07 ` |PENDING| " dpdklab
2024-07-03 13:09 ` |FAILURE| " dpdklab
2024-07-03 13:27 ` |PENDING| " dpdklab
2024-07-03 13:31 ` |FAILURE| " dpdklab
2024-07-03 13:31 ` dpdklab
2024-07-03 13:32 ` dpdklab
2024-07-03 13:32 ` dpdklab
2024-07-03 13:34 ` |PENDING| " dpdklab
2024-07-03 14:13 ` dpdklab
2024-07-03 14:20 ` dpdklab
2024-07-03 14:23 ` |SUCCESS| " dpdklab
2024-07-03 15:04 ` dpdklab
2024-07-03 18:12 ` |PENDING| " dpdklab
2024-07-03 18:15 ` dpdklab
2024-07-03 18:22 ` dpdklab
2024-07-03 18:29 ` dpdklab
2024-07-03 20:47 ` dpdklab
2024-07-03 21:10 ` dpdklab
2024-07-03 21:17 ` dpdklab
2024-07-03 21:18 ` dpdklab
2024-07-03 21:24 ` dpdklab
2024-07-03 21:32 ` dpdklab
2024-07-03 21:38 ` dpdklab
2024-07-03 21:40 ` dpdklab
2024-07-03 21:46 ` dpdklab
2024-07-03 21:48 ` dpdklab
2024-07-04 2:15 ` dpdklab
2024-07-04 2:20 ` |SUCCESS| " dpdklab
2024-07-04 7:53 ` dpdklab
2024-07-04 9:41 ` 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=20240703082204.883B3128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xiangwencheng@dayudpu.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).