From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141484 [RFC PATCH v2] Initial Implementation For Jumbo Frames Test Suite
Date: Fri, 21 Jun 2024 18:24:00 -0400 [thread overview]
Message-ID: <20240621222400.1668759-1-robot@bytheb.org> (raw)
In-Reply-To: <20240621211920.14286-2-npratte@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141484/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9620153084
next prev parent reply other threads:[~2024-06-21 22:24 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240621211920.14286-2-npratte@iol.unh.edu>
2024-06-21 20:53 ` qemudev
2024-06-21 20:57 ` qemudev
2024-06-21 21:20 ` checkpatch
2024-06-21 22:24 ` 0-day Robot [this message]
2024-06-21 23:49 ` |SUCCESS| pw141484 [PATCH] [RFC,v2] Initial Implementation For Jumbo dpdklab
2024-06-21 23:51 ` dpdklab
2024-06-21 23:53 ` dpdklab
2024-06-21 23:57 ` dpdklab
2024-06-21 23:57 ` dpdklab
2024-06-21 23:58 ` dpdklab
2024-06-22 0:15 ` dpdklab
2024-06-22 0:16 ` dpdklab
2024-06-22 0:17 ` dpdklab
2024-06-22 0:17 ` dpdklab
2024-06-22 0:18 ` dpdklab
2024-06-22 0:19 ` dpdklab
2024-06-22 0:21 ` dpdklab
2024-06-22 0:21 ` dpdklab
2024-06-22 0:21 ` dpdklab
2024-06-22 0:21 ` dpdklab
2024-06-22 0:22 ` dpdklab
2024-06-22 0:23 ` dpdklab
2024-06-22 0:29 ` dpdklab
2024-06-22 0:31 ` dpdklab
2024-06-22 0:35 ` dpdklab
2024-06-22 0:37 ` dpdklab
2024-06-22 0:41 ` dpdklab
2024-06-22 0:44 ` dpdklab
2024-06-22 0:44 ` dpdklab
2024-06-22 0:44 ` dpdklab
2024-06-22 0:45 ` dpdklab
2024-06-22 0:45 ` dpdklab
2024-06-22 0:46 ` dpdklab
2024-06-22 0:47 ` dpdklab
2024-06-22 0:48 ` dpdklab
2024-06-22 0:48 ` dpdklab
2024-06-22 0:49 ` dpdklab
2024-06-22 0:50 ` dpdklab
2024-06-22 0:50 ` dpdklab
2024-06-22 0:50 ` dpdklab
2024-06-22 0:50 ` dpdklab
2024-06-22 0:50 ` dpdklab
2024-06-22 0:51 ` dpdklab
2024-06-22 0:52 ` dpdklab
2024-06-22 0:54 ` dpdklab
2024-06-22 0:55 ` dpdklab
2024-06-22 0:55 ` dpdklab
2024-06-22 0:56 ` dpdklab
2024-06-22 0:58 ` dpdklab
2024-06-22 0:58 ` dpdklab
2024-06-22 0:58 ` dpdklab
2024-06-22 0:59 ` dpdklab
2024-06-22 0:59 ` dpdklab
2024-06-22 1:00 ` dpdklab
2024-06-22 1:15 ` dpdklab
2024-06-22 1:16 ` dpdklab
2024-06-22 1:17 ` dpdklab
2024-06-22 1:17 ` dpdklab
2024-06-22 1:18 ` dpdklab
2024-06-22 1:19 ` dpdklab
2024-06-22 1:19 ` dpdklab
2024-06-22 1:20 ` dpdklab
2024-06-22 1:20 ` dpdklab
2024-06-22 1:20 ` dpdklab
2024-06-22 1:21 ` dpdklab
2024-06-22 1:21 ` dpdklab
2024-06-22 1:21 ` dpdklab
2024-06-22 1:21 ` dpdklab
2024-06-22 1:21 ` dpdklab
2024-06-22 1:22 ` dpdklab
2024-06-22 1:22 ` dpdklab
2024-06-22 1:22 ` dpdklab
2024-06-22 1:23 ` dpdklab
2024-06-22 1:23 ` dpdklab
2024-06-22 1:23 ` dpdklab
2024-06-22 1:23 ` dpdklab
2024-06-22 1:24 ` dpdklab
2024-06-22 1:24 ` dpdklab
2024-06-22 1:24 ` dpdklab
2024-06-22 1:24 ` dpdklab
2024-06-22 1:24 ` dpdklab
2024-06-22 1:25 ` dpdklab
2024-06-22 1:25 ` dpdklab
2024-06-22 1:25 ` dpdklab
2024-06-22 1:25 ` dpdklab
2024-06-22 1:25 ` dpdklab
2024-06-22 1:25 ` dpdklab
2024-06-22 1:26 ` dpdklab
2024-06-22 1:26 ` dpdklab
2024-06-22 1:26 ` dpdklab
2024-06-22 1:27 ` dpdklab
2024-06-22 1:27 ` dpdklab
2024-06-22 1:28 ` dpdklab
2024-06-22 1:28 ` dpdklab
2024-06-22 1:28 ` dpdklab
2024-06-22 1:29 ` dpdklab
2024-06-22 1:29 ` dpdklab
2024-06-22 1:30 ` dpdklab
2024-06-22 1:30 ` dpdklab
2024-06-22 1:31 ` dpdklab
2024-06-22 1:32 ` dpdklab
2024-06-22 1:40 ` dpdklab
2024-06-22 1:44 ` dpdklab
2024-06-22 1:45 ` dpdklab
2024-06-22 1:46 ` dpdklab
2024-06-22 1:48 ` dpdklab
2024-06-22 1:49 ` dpdklab
2024-06-22 2:01 ` dpdklab
2024-06-22 2:01 ` dpdklab
2024-06-22 2:07 ` dpdklab
2024-06-22 2:10 ` dpdklab
2024-06-22 2:20 ` dpdklab
2024-06-22 2:26 ` dpdklab
2024-06-22 13:49 ` 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=20240621222400.1668759-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).