From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141292 [PATCH 5/5] ipfrag: use accelerated crc on riscv
Date: Tue, 18 Jun 2024 14:44:32 -0400 [thread overview]
Message-ID: <20240618184432.1581091-1-robot@bytheb.org> (raw)
In-Reply-To: <20240618174133.33457-6-daniel.gregory@bytedance.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141292/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9569996856
next prev parent reply other threads:[~2024-06-18 18:44 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618174133.33457-6-daniel.gregory@bytedance.com>
2024-06-18 17:16 ` |SUCCESS| pw141288-141292 " qemudev
2024-06-18 17:20 ` qemudev
2024-06-18 17:44 ` |SUCCESS| pw141292 " checkpatch
2024-06-18 18:44 ` 0-day Robot [this message]
2024-06-18 22:35 ` |SUCCESS| pw141288-141292 [PATCH] [5/5] ipfrag: use accelerated crc dpdklab
2024-06-18 22:36 ` dpdklab
2024-06-18 22:37 ` dpdklab
2024-06-18 22:37 ` dpdklab
2024-06-18 22:37 ` dpdklab
2024-06-18 22:37 ` dpdklab
2024-06-18 22:39 ` dpdklab
2024-06-18 22:39 ` dpdklab
2024-06-18 22:39 ` dpdklab
2024-06-18 22:41 ` dpdklab
2024-06-18 22:43 ` dpdklab
2024-06-18 22:45 ` dpdklab
2024-06-18 22:48 ` dpdklab
2024-06-18 22:49 ` dpdklab
2024-06-18 23:15 ` dpdklab
2024-06-18 23:25 ` dpdklab
2024-06-19 0:31 ` dpdklab
2024-06-19 0:33 ` dpdklab
2024-06-19 0:33 ` dpdklab
2024-06-19 0:34 ` dpdklab
2024-06-19 0:34 ` dpdklab
2024-06-19 0:35 ` dpdklab
2024-06-19 0:35 ` dpdklab
2024-06-19 0:37 ` dpdklab
2024-06-19 0:37 ` dpdklab
2024-06-19 1:02 ` dpdklab
2024-06-19 1:02 ` dpdklab
2024-06-19 1:02 ` dpdklab
2024-06-19 1:03 ` dpdklab
2024-06-19 1:04 ` dpdklab
2024-06-19 1:04 ` dpdklab
2024-06-19 1:06 ` dpdklab
2024-06-19 1:07 ` dpdklab
2024-06-19 1:08 ` dpdklab
2024-06-19 1:08 ` dpdklab
2024-06-19 1:14 ` dpdklab
2024-06-19 1:18 ` dpdklab
2024-06-19 1:24 ` dpdklab
2024-06-19 2:22 ` dpdklab
2024-06-19 3:39 ` dpdklab
2024-06-19 3:46 ` dpdklab
2024-06-19 3:48 ` dpdklab
2024-06-19 3:52 ` dpdklab
2024-06-19 3:55 ` dpdklab
2024-06-19 3:55 ` dpdklab
2024-06-19 4:08 ` dpdklab
2024-06-19 4:24 ` dpdklab
2024-06-19 4:26 ` dpdklab
2024-06-19 4:26 ` dpdklab
2024-06-19 4:27 ` dpdklab
2024-06-19 4:30 ` dpdklab
2024-06-19 4:37 ` dpdklab
2024-06-19 4:38 ` dpdklab
2024-06-19 4:45 ` dpdklab
2024-06-19 5:02 ` dpdklab
2024-06-19 5:18 ` dpdklab
2024-06-19 5:20 ` dpdklab
2024-06-19 5:21 ` dpdklab
2024-06-19 5:22 ` dpdklab
2024-06-19 5:23 ` dpdklab
2024-06-19 5:24 ` dpdklab
2024-06-19 5:25 ` dpdklab
2024-06-19 5:26 ` dpdklab
2024-06-19 5:30 ` dpdklab
2024-06-19 5:31 ` dpdklab
2024-06-19 5:32 ` dpdklab
2024-06-19 5:34 ` dpdklab
2024-06-19 5:41 ` dpdklab
2024-06-19 5:43 ` dpdklab
2024-06-19 5:44 ` dpdklab
2024-06-19 5:44 ` dpdklab
2024-06-19 5:46 ` dpdklab
2024-06-19 5:48 ` dpdklab
2024-06-19 5:49 ` dpdklab
2024-06-19 5:49 ` dpdklab
2024-06-19 5:50 ` dpdklab
2024-06-19 5:50 ` dpdklab
2024-06-19 5:52 ` dpdklab
2024-06-19 5:52 ` dpdklab
2024-06-19 5:53 ` dpdklab
2024-06-19 5:53 ` dpdklab
2024-06-19 5:53 ` dpdklab
2024-06-19 5:54 ` dpdklab
2024-06-19 5:55 ` dpdklab
2024-06-19 6:02 ` dpdklab
2024-06-19 6:05 ` dpdklab
2024-06-19 6:16 ` dpdklab
2024-06-19 6:17 ` dpdklab
2024-06-19 6:20 ` dpdklab
2024-06-19 6:22 ` dpdklab
2024-06-19 6:26 ` dpdklab
2024-06-19 7:09 ` dpdklab
2024-06-19 7:12 ` dpdklab
2024-06-19 7:30 ` dpdklab
2024-06-19 7:30 ` dpdklab
2024-06-19 7:38 ` dpdklab
2024-06-19 7:54 ` dpdklab
2024-06-19 8:03 ` dpdklab
2024-06-19 8:04 ` dpdklab
2024-06-19 8:05 ` dpdklab
2024-06-19 8:07 ` dpdklab
2024-06-19 8:07 ` dpdklab
2024-06-19 8:08 ` dpdklab
2024-06-19 8:26 ` dpdklab
2024-06-19 8:28 ` dpdklab
2024-06-19 8:42 ` dpdklab
2024-06-19 9:17 ` dpdklab
2024-06-19 14:51 ` dpdklab
2024-06-19 15:32 ` dpdklab
2024-06-20 18:21 ` 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=20240618184432.1581091-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).