From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141508 [PATCH] app/testpmd: fix help string of BPF load command
Date: Sun, 23 Jun 2024 23:04:15 -0400 [thread overview]
Message-ID: <20240624030415.1895243-1-robot@bytheb.org> (raw)
In-Reply-To: <20240624015852.3712910-1-chaoyong.he@corigine.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141508/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9638599039
next prev parent reply other threads:[~2024-06-24 3:04 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624015852.3712910-1-chaoyong.he@corigine.com>
2024-06-24 1:35 ` qemudev
2024-06-24 1:39 ` qemudev
2024-06-24 2:01 ` checkpatch
2024-06-24 2:47 ` |SUCCESS| pw141508 [PATCH] app/testpmd: fix help string of BPF load dpdklab
2024-06-24 2:47 ` dpdklab
2024-06-24 2:48 ` dpdklab
2024-06-24 2:48 ` dpdklab
2024-06-24 2:48 ` dpdklab
2024-06-24 2:49 ` dpdklab
2024-06-24 2:49 ` dpdklab
2024-06-24 2:49 ` dpdklab
2024-06-24 2:49 ` dpdklab
2024-06-24 2:50 ` dpdklab
2024-06-24 2:50 ` dpdklab
2024-06-24 2:50 ` dpdklab
2024-06-24 2:51 ` dpdklab
2024-06-24 2:51 ` dpdklab
2024-06-24 2:51 ` dpdklab
2024-06-24 2:51 ` dpdklab
2024-06-24 2:52 ` dpdklab
2024-06-24 2:52 ` dpdklab
2024-06-24 2:52 ` dpdklab
2024-06-24 2:52 ` dpdklab
2024-06-24 2:53 ` dpdklab
2024-06-24 2:53 ` dpdklab
2024-06-24 2:53 ` dpdklab
2024-06-24 2:54 ` dpdklab
2024-06-24 2:54 ` dpdklab
2024-06-24 2:54 ` dpdklab
2024-06-24 2:54 ` dpdklab
2024-06-24 2:55 ` dpdklab
2024-06-24 2:55 ` dpdklab
2024-06-24 2:55 ` dpdklab
2024-06-24 2:55 ` dpdklab
2024-06-24 2:55 ` dpdklab
2024-06-24 2:55 ` dpdklab
2024-06-24 2:56 ` dpdklab
2024-06-24 2:56 ` dpdklab
2024-06-24 2:56 ` dpdklab
2024-06-24 2:56 ` dpdklab
2024-06-24 2:57 ` dpdklab
2024-06-24 2:57 ` dpdklab
2024-06-24 2:58 ` dpdklab
2024-06-24 2:58 ` dpdklab
2024-06-24 2:58 ` dpdklab
2024-06-24 2:58 ` dpdklab
2024-06-24 2:59 ` dpdklab
2024-06-24 2:59 ` dpdklab
2024-06-24 2:59 ` dpdklab
2024-06-24 2:59 ` dpdklab
2024-06-24 2:59 ` dpdklab
2024-06-24 3:00 ` dpdklab
2024-06-24 3:00 ` dpdklab
2024-06-24 3:00 ` dpdklab
2024-06-24 3:01 ` dpdklab
2024-06-24 3:02 ` dpdklab
2024-06-24 3:02 ` dpdklab
2024-06-24 3:03 ` dpdklab
2024-06-24 3:03 ` dpdklab
2024-06-24 3:04 ` dpdklab
2024-06-24 3:04 ` 0-day Robot [this message]
2024-06-24 3:04 ` dpdklab
2024-06-24 3:04 ` dpdklab
2024-06-24 3:05 ` dpdklab
2024-06-24 3:05 ` dpdklab
2024-06-24 3:06 ` dpdklab
2024-06-24 3:06 ` dpdklab
2024-06-24 3:07 ` dpdklab
2024-06-24 3:07 ` dpdklab
2024-06-24 3:08 ` dpdklab
2024-06-24 3:09 ` dpdklab
2024-06-24 3:09 ` dpdklab
2024-06-24 3:10 ` dpdklab
2024-06-24 3:11 ` dpdklab
2024-06-24 3:11 ` dpdklab
2024-06-24 3:12 ` dpdklab
2024-06-24 3:13 ` dpdklab
2024-06-24 3:14 ` dpdklab
2024-06-24 3:14 ` dpdklab
2024-06-24 3:14 ` dpdklab
2024-06-24 3:15 ` dpdklab
2024-06-24 3:15 ` dpdklab
2024-06-24 3:20 ` dpdklab
2024-06-24 3:20 ` dpdklab
2024-06-24 3:20 ` dpdklab
2024-06-24 3:22 ` dpdklab
2024-06-24 3:22 ` dpdklab
2024-06-24 3:23 ` dpdklab
2024-06-24 3:23 ` dpdklab
2024-06-24 3:24 ` dpdklab
2024-06-24 3:24 ` dpdklab
2024-06-24 3:25 ` dpdklab
2024-06-24 3:27 ` dpdklab
2024-06-24 3:27 ` dpdklab
2024-06-24 3:27 ` dpdklab
2024-06-24 3:28 ` dpdklab
2024-06-24 3:28 ` dpdklab
2024-06-24 3:29 ` dpdklab
2024-06-24 3:29 ` dpdklab
2024-06-24 3:31 ` dpdklab
2024-06-24 3:33 ` dpdklab
2024-06-24 3:33 ` dpdklab
2024-06-24 3:35 ` dpdklab
2024-06-24 3:35 ` dpdklab
2024-06-24 3:36 ` dpdklab
2024-06-24 3:36 ` dpdklab
2024-06-24 3:37 ` dpdklab
2024-06-24 3:39 ` dpdklab
2024-06-24 3:40 ` dpdklab
2024-06-24 3:43 ` dpdklab
2024-06-24 3:44 ` dpdklab
2024-06-24 3:58 ` dpdklab
2024-06-24 4:01 ` dpdklab
2024-06-24 5:12 ` 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=20240624030415.1895243-1-robot@bytheb.org \
--to=robot@bytheb.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).