From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: zhaoxinxin <15957197901@163.com>
Subject: |WARNING| pw141595 [PATCH] vhost: Fix the crash caused by accessing the released memory
Date: Tue, 25 Jun 2024 08:41:22 +0200 (CEST) [thread overview]
Message-ID: <20240625064122.9B782128144@dpdk.org> (raw)
In-Reply-To: <20240625021347.63978-1-15957197901@163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141595
_coding style issues_
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: zhaoxinxin <15957197901@163.com>' != 'Signed-off-by: Xinxin Zhao <15957197901@163.com>'
total: 0 errors, 1 warnings, 8 lines checked
next prev parent reply other threads:[~2024-06-25 6:41 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240625021347.63978-1-15957197901@163.com>
2024-06-25 6:15 ` |SUCCESS| " qemudev
2024-06-25 6:20 ` qemudev
2024-06-25 6:41 ` checkpatch [this message]
2024-06-25 11:46 ` |SUCCESS| pw141595 [PATCH] vhost: Fix the crash caused by accessing dpdklab
2024-06-25 11:46 ` dpdklab
2024-06-25 11:46 ` dpdklab
2024-06-25 11:46 ` dpdklab
2024-06-25 11:46 ` dpdklab
2024-06-25 11:47 ` dpdklab
2024-06-25 11:48 ` dpdklab
2024-06-25 11:49 ` dpdklab
2024-06-25 11:49 ` dpdklab
2024-06-25 11:49 ` dpdklab
2024-06-25 11:50 ` dpdklab
2024-06-25 11:51 ` dpdklab
2024-06-25 11:52 ` dpdklab
2024-06-25 11:54 ` dpdklab
2024-06-25 11:54 ` dpdklab
2024-06-25 11:55 ` dpdklab
2024-06-25 11:57 ` dpdklab
2024-06-25 12:07 ` dpdklab
2024-06-25 12:09 ` dpdklab
2024-06-25 12:10 ` dpdklab
2024-06-25 12:11 ` dpdklab
2024-06-25 12:15 ` dpdklab
2024-06-25 12:17 ` dpdklab
2024-06-25 12:17 ` dpdklab
2024-06-25 12:18 ` dpdklab
2024-06-25 12:26 ` dpdklab
2024-06-25 12:27 ` dpdklab
2024-06-25 12:29 ` dpdklab
2024-06-25 12:30 ` dpdklab
2024-06-25 12:30 ` dpdklab
2024-06-25 12:31 ` dpdklab
2024-06-25 12:40 ` dpdklab
2024-06-25 13:08 ` dpdklab
2024-06-25 13:11 ` dpdklab
2024-06-25 13:12 ` dpdklab
2024-06-25 13:16 ` dpdklab
2024-06-25 13:16 ` dpdklab
2024-06-25 13:18 ` dpdklab
2024-06-25 13:19 ` dpdklab
2024-06-25 13:20 ` dpdklab
2024-06-25 13:21 ` dpdklab
2024-06-25 13:21 ` dpdklab
2024-06-25 13:22 ` dpdklab
2024-06-25 13:23 ` dpdklab
2024-06-25 13:25 ` dpdklab
2024-06-25 13:27 ` dpdklab
2024-06-25 13:27 ` dpdklab
2024-06-25 13:28 ` dpdklab
2024-06-25 13:28 ` dpdklab
2024-06-25 13:29 ` dpdklab
2024-06-25 13:30 ` dpdklab
2024-06-25 13:31 ` dpdklab
2024-06-25 13:32 ` dpdklab
2024-06-25 13:35 ` dpdklab
2024-06-25 13:36 ` dpdklab
2024-06-25 13:37 ` dpdklab
2024-06-25 13:40 ` dpdklab
2024-06-25 13:41 ` dpdklab
2024-06-25 13:42 ` dpdklab
2024-06-25 13:42 ` dpdklab
2024-06-25 13:45 ` dpdklab
2024-06-25 13:47 ` dpdklab
2024-06-25 13:49 ` dpdklab
2024-06-25 13:50 ` dpdklab
2024-06-25 13:50 ` dpdklab
2024-06-25 13:50 ` dpdklab
2024-06-25 13:52 ` dpdklab
2024-06-25 13:53 ` dpdklab
2024-06-25 13:54 ` dpdklab
2024-06-25 13:54 ` dpdklab
2024-06-25 13:55 ` dpdklab
2024-06-25 13:55 ` dpdklab
2024-06-25 13:55 ` dpdklab
2024-06-25 13:56 ` dpdklab
2024-06-25 13:56 ` dpdklab
2024-06-25 13:57 ` dpdklab
2024-06-25 13:58 ` dpdklab
2024-06-25 14:05 ` dpdklab
2024-06-25 14:05 ` dpdklab
2024-06-25 14:06 ` dpdklab
2024-06-25 14:06 ` dpdklab
2024-06-25 14:06 ` dpdklab
2024-06-25 14:07 ` dpdklab
2024-06-25 14:07 ` dpdklab
2024-06-25 14:07 ` dpdklab
2024-06-25 14:08 ` dpdklab
2024-06-25 14:08 ` dpdklab
2024-06-25 14:08 ` dpdklab
2024-06-25 14:08 ` dpdklab
2024-06-25 14:08 ` dpdklab
2024-06-25 14:08 ` dpdklab
2024-06-25 14:09 ` dpdklab
2024-06-25 14:09 ` dpdklab
2024-06-25 14:09 ` dpdklab
2024-06-25 14:09 ` dpdklab
2024-06-25 14:09 ` dpdklab
2024-06-25 14:09 ` dpdklab
2024-06-25 14:10 ` dpdklab
2024-06-25 14:10 ` dpdklab
2024-06-25 14:10 ` dpdklab
2024-06-25 14:14 ` dpdklab
2024-06-25 14:37 ` dpdklab
2024-06-25 14:39 ` dpdklab
2024-06-25 14:42 ` dpdklab
2024-06-25 14:44 ` dpdklab
2024-06-25 14:46 ` dpdklab
2024-06-25 15:44 ` 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=20240625064122.9B782128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=15957197901@163.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).