From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138739 [PATCH v2] graph: fix head move when graph walk in mcore dispatch
Date: Fri, 22 Mar 2024 08:56:03 +0100 (CET) [thread overview]
Message-ID: <20240322075603.BEF6C1223F9@dpdk.org> (raw)
In-Reply-To: <20240322154637.1346239-1-jingjing.wu@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138739
_coding style OK_
next prev parent reply other threads:[~2024-03-22 7:56 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322154637.1346239-1-jingjing.wu@intel.com>
2024-03-22 7:31 ` qemudev
2024-03-22 7:36 ` qemudev
2024-03-22 7:56 ` checkpatch [this message]
2024-03-22 8:45 ` 0-day Robot
2024-03-22 17:24 ` |SUCCESS| pw138739 [PATCH] [v2] graph: fix head move when graph walk dpdklab
2024-03-22 17:30 ` dpdklab
2024-03-22 17:30 ` dpdklab
2024-03-22 17:30 ` dpdklab
2024-03-22 17:31 ` dpdklab
2024-03-22 17:31 ` dpdklab
2024-03-22 17:31 ` dpdklab
2024-03-22 17:32 ` dpdklab
2024-03-22 17:32 ` dpdklab
2024-03-22 17:33 ` dpdklab
2024-03-22 17:34 ` dpdklab
2024-03-22 17:34 ` dpdklab
2024-03-22 17:34 ` dpdklab
2024-03-22 17:35 ` dpdklab
2024-03-22 17:35 ` dpdklab
2024-03-22 17:37 ` dpdklab
2024-03-22 17:37 ` dpdklab
2024-03-22 17:38 ` dpdklab
2024-03-22 17:38 ` dpdklab
2024-03-22 17:39 ` dpdklab
2024-03-22 17:39 ` dpdklab
2024-03-22 17:40 ` dpdklab
2024-03-22 17:40 ` dpdklab
2024-03-22 17:40 ` dpdklab
2024-03-22 17:41 ` dpdklab
2024-03-22 17:41 ` dpdklab
2024-03-22 17:41 ` dpdklab
2024-03-22 17:41 ` dpdklab
2024-03-22 17:42 ` dpdklab
2024-03-22 17:42 ` dpdklab
2024-03-22 17:42 ` dpdklab
2024-03-22 17:43 ` dpdklab
2024-03-22 17:43 ` dpdklab
2024-03-22 17:49 ` dpdklab
2024-03-22 17:49 ` dpdklab
2024-03-22 17:50 ` dpdklab
2024-03-22 17:50 ` dpdklab
2024-03-22 17:50 ` dpdklab
2024-03-22 17:52 ` dpdklab
2024-03-22 17:52 ` dpdklab
2024-03-22 17:52 ` dpdklab
2024-03-22 17:54 ` dpdklab
2024-03-22 17:59 ` dpdklab
2024-03-22 17:59 ` dpdklab
2024-03-22 18:00 ` dpdklab
2024-03-22 18:00 ` dpdklab
2024-03-22 18:00 ` dpdklab
2024-03-22 18:00 ` dpdklab
2024-03-22 18:00 ` dpdklab
2024-03-22 18:01 ` dpdklab
2024-03-22 18:01 ` dpdklab
2024-03-22 18:07 ` dpdklab
2024-03-22 18:08 ` dpdklab
2024-03-22 18:08 ` dpdklab
2024-03-22 18:09 ` dpdklab
2024-03-22 18:10 ` dpdklab
2024-03-22 18:10 ` dpdklab
2024-03-22 18:12 ` dpdklab
2024-03-22 18:14 ` dpdklab
2024-03-22 18:14 ` dpdklab
2024-03-22 18:15 ` dpdklab
2024-03-22 18:15 ` dpdklab
2024-03-22 18:16 ` dpdklab
2024-03-22 18:16 ` dpdklab
2024-03-22 18:16 ` dpdklab
2024-03-22 18:17 ` dpdklab
2024-03-22 18:19 ` dpdklab
2024-03-22 18:19 ` dpdklab
2024-03-22 18:25 ` dpdklab
2024-03-22 18:26 ` dpdklab
2024-03-22 18:26 ` dpdklab
2024-03-22 18:43 ` dpdklab
2024-03-22 18:57 ` dpdklab
2024-03-24 3:56 ` dpdklab
2024-03-24 4:46 ` 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=20240322075603.BEF6C1223F9@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).