From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a freed vsocket
Date: Wed, 3 Apr 2024 05:27:32 +0200 (CEST) [thread overview]
Message-ID: <20240403032732.3BA791223FE@dpdk.org> (raw)
In-Reply-To: <TYAP286MB0649A160A9852720E0F3D67BD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139067
_coding style OK_
next prev parent reply other threads:[~2024-04-03 3:27 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYAP286MB0649A160A9852720E0F3D67BD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-04-03 3:03 ` qemudev
2024-04-03 3:27 ` checkpatch [this message]
2024-04-03 4:25 ` |FAILURE| " 0-day Robot
2024-04-03 8:22 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a fr dpdklab
2024-04-03 8:24 ` dpdklab
2024-04-03 8:27 ` dpdklab
2024-04-03 8:33 ` dpdklab
2024-04-03 8:33 ` dpdklab
2024-04-03 8:39 ` dpdklab
2024-04-03 8:53 ` dpdklab
2024-04-03 8:53 ` dpdklab
2024-04-03 8:54 ` dpdklab
2024-04-03 8:55 ` dpdklab
2024-04-03 8:55 ` dpdklab
2024-04-03 8:56 ` dpdklab
2024-04-03 8:56 ` dpdklab
2024-04-03 8:56 ` dpdklab
2024-04-03 8:57 ` dpdklab
2024-04-03 8:57 ` dpdklab
2024-04-03 8:57 ` dpdklab
2024-04-03 8:58 ` dpdklab
2024-04-03 8:58 ` dpdklab
2024-04-03 8:59 ` dpdklab
2024-04-03 9:15 ` |FAILURE| " dpdklab
2024-04-03 9:16 ` dpdklab
2024-04-03 9:17 ` dpdklab
2024-04-03 9:18 ` dpdklab
2024-04-03 9:19 ` dpdklab
2024-04-03 9:19 ` dpdklab
2024-04-03 9:20 ` |SUCCESS| " dpdklab
2024-04-03 9:22 ` |FAILURE| " dpdklab
2024-04-03 9:23 ` dpdklab
2024-04-03 9:23 ` dpdklab
2024-04-03 9:24 ` dpdklab
2024-04-03 9:24 ` dpdklab
2024-04-03 9:24 ` dpdklab
2024-04-03 9:25 ` dpdklab
2024-04-03 9:25 ` dpdklab
2024-04-03 9:25 ` dpdklab
2024-04-03 9:26 ` dpdklab
2024-04-03 9:26 ` dpdklab
2024-04-03 9:26 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` |SUCCESS| " dpdklab
2024-04-03 9:29 ` |FAILURE| " dpdklab
2024-04-03 9:29 ` dpdklab
2024-04-03 9:29 ` dpdklab
2024-04-03 9:30 ` dpdklab
2024-04-03 9:30 ` |SUCCESS| " dpdklab
2024-04-03 9:30 ` |FAILURE| " dpdklab
2024-04-03 9:31 ` dpdklab
2024-04-03 9:31 ` dpdklab
2024-04-03 9:32 ` dpdklab
2024-04-03 9:32 ` dpdklab
2024-04-03 9:32 ` dpdklab
2024-04-03 9:33 ` dpdklab
2024-04-03 9:34 ` dpdklab
2024-04-03 9:35 ` dpdklab
2024-04-03 9:36 ` |SUCCESS| " dpdklab
2024-04-03 9:37 ` dpdklab
2024-04-03 9:37 ` |FAILURE| " dpdklab
2024-04-03 9:38 ` dpdklab
2024-04-03 9:39 ` dpdklab
2024-04-03 9:40 ` dpdklab
2024-04-03 9:40 ` dpdklab
2024-04-03 9:42 ` dpdklab
2024-04-03 9:44 ` dpdklab
2024-04-03 9:44 ` dpdklab
2024-04-03 9:45 ` dpdklab
2024-04-03 9:46 ` dpdklab
2024-04-03 9:52 ` dpdklab
2024-04-03 9:52 ` dpdklab
2024-04-03 10:11 ` dpdklab
2024-04-03 11:01 ` dpdklab
2024-04-03 11:03 ` dpdklab
2024-04-03 11:18 ` |SUCCESS| " dpdklab
2024-04-03 13:08 ` |FAILURE| " dpdklab
2024-04-03 13:35 ` |SUCCESS| " dpdklab
2024-04-03 13:55 ` dpdklab
2024-04-04 4:00 ` dpdklab
2024-04-04 4:30 ` dpdklab
2024-04-04 5:13 ` dpdklab
2024-04-04 5:56 ` dpdklab
2024-04-04 6:01 ` dpdklab
2024-04-07 1:11 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a freed vsocket qemudev
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=20240403032732.3BA791223FE@dpdk.org \
--to=checkpatch@dpdk.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).