From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141231 [PATCH] net: add bit fields to IPv6 header definition
Date: Tue, 18 Jun 2024 02:24:32 -0400 [thread overview]
Message-ID: <20240618062432.4094958-1-robot@bytheb.org> (raw)
In-Reply-To: <20240618051751.220610-1-getelson@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141231/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9559656736
next prev parent reply other threads:[~2024-06-18 6:24 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618051751.220610-1-getelson@nvidia.com>
2024-06-18 4:52 ` qemudev
2024-06-18 4:57 ` qemudev
2024-06-18 5:19 ` checkpatch
2024-06-18 6:24 ` 0-day Robot [this message]
2024-06-18 7:12 ` |SUCCESS| pw141231 [PATCH] net: add bit fields to IPv6 header defini dpdklab
2024-06-18 7:13 ` dpdklab
2024-06-18 7:18 ` dpdklab
2024-06-18 7:22 ` dpdklab
2024-06-18 7:24 ` dpdklab
2024-06-18 7:33 ` dpdklab
2024-06-18 7:38 ` dpdklab
2024-06-18 7:40 ` dpdklab
2024-06-18 7:47 ` dpdklab
2024-06-18 7:50 ` dpdklab
2024-06-18 7:53 ` dpdklab
2024-06-18 7:56 ` dpdklab
2024-06-18 7:58 ` dpdklab
2024-06-18 7:59 ` dpdklab
2024-06-18 8:00 ` dpdklab
2024-06-18 8:59 ` dpdklab
2024-06-18 9:01 ` dpdklab
2024-06-18 9:07 ` dpdklab
2024-06-18 9:08 ` dpdklab
2024-06-18 9:09 ` dpdklab
2024-06-18 9:13 ` dpdklab
2024-06-18 9:14 ` dpdklab
2024-06-18 9:16 ` dpdklab
2024-06-18 9:18 ` dpdklab
2024-06-18 9:19 ` dpdklab
2024-06-18 9:20 ` dpdklab
2024-06-18 9:23 ` dpdklab
2024-06-18 10:09 ` dpdklab
2024-06-18 10:10 ` dpdklab
2024-06-18 10:12 ` dpdklab
2024-06-18 10:12 ` dpdklab
2024-06-18 10:12 ` dpdklab
2024-06-18 10:12 ` dpdklab
2024-06-18 10:13 ` dpdklab
2024-06-18 10:13 ` dpdklab
2024-06-18 10:13 ` dpdklab
2024-06-18 10:14 ` dpdklab
2024-06-18 10:16 ` dpdklab
2024-06-18 10:18 ` dpdklab
2024-06-18 10:18 ` dpdklab
2024-06-18 10:19 ` dpdklab
2024-06-18 10:20 ` dpdklab
2024-06-18 10:20 ` dpdklab
2024-06-18 10:23 ` dpdklab
2024-06-18 10:27 ` dpdklab
2024-06-18 10:28 ` dpdklab
2024-06-18 10:28 ` dpdklab
2024-06-18 10:29 ` dpdklab
2024-06-18 10:30 ` dpdklab
2024-06-18 10:30 ` dpdklab
2024-06-18 10:32 ` dpdklab
2024-06-18 10:33 ` dpdklab
2024-06-18 10:34 ` dpdklab
2024-06-18 10:35 ` dpdklab
2024-06-18 10:36 ` dpdklab
2024-06-18 10:37 ` dpdklab
2024-06-18 10:37 ` dpdklab
2024-06-18 10:37 ` dpdklab
2024-06-18 10:38 ` dpdklab
2024-06-18 10:38 ` dpdklab
2024-06-18 10:38 ` dpdklab
2024-06-18 10:39 ` dpdklab
2024-06-18 10:39 ` dpdklab
2024-06-18 10:40 ` dpdklab
2024-06-18 10:41 ` dpdklab
2024-06-18 10:41 ` dpdklab
2024-06-18 10:42 ` dpdklab
2024-06-18 10:42 ` dpdklab
2024-06-18 10:42 ` dpdklab
2024-06-18 10:42 ` dpdklab
2024-06-18 10:43 ` dpdklab
2024-06-18 10:43 ` dpdklab
2024-06-18 10:43 ` dpdklab
2024-06-18 10:44 ` dpdklab
2024-06-18 10:44 ` dpdklab
2024-06-18 10:44 ` dpdklab
2024-06-18 10:50 ` dpdklab
2024-06-18 10:50 ` dpdklab
2024-06-18 10:50 ` dpdklab
2024-06-18 10:51 ` dpdklab
2024-06-18 10:52 ` dpdklab
2024-06-18 10:52 ` dpdklab
2024-06-18 10:52 ` dpdklab
2024-06-18 10:53 ` dpdklab
2024-06-18 10:54 ` dpdklab
2024-06-18 10:54 ` dpdklab
2024-06-18 10:54 ` dpdklab
2024-06-18 10:56 ` dpdklab
2024-06-18 11:01 ` dpdklab
2024-06-18 11:02 ` dpdklab
2024-06-18 11:02 ` dpdklab
2024-06-18 11:03 ` dpdklab
2024-06-18 11:04 ` dpdklab
2024-06-18 11:04 ` dpdklab
2024-06-18 11:04 ` dpdklab
2024-06-18 11:05 ` dpdklab
2024-06-18 11:06 ` dpdklab
2024-06-18 11:07 ` dpdklab
2024-06-18 11:08 ` dpdklab
2024-06-18 11:08 ` dpdklab
2024-06-18 11:14 ` dpdklab
2024-06-18 11:15 ` dpdklab
2024-06-18 11:29 ` dpdklab
2024-06-18 12:16 ` dpdklab
2024-06-18 12:19 ` dpdklab
2024-06-18 13:05 ` dpdklab
2024-06-18 13:23 ` dpdklab
2024-06-18 13:42 ` dpdklab
2024-06-18 15:44 ` dpdklab
2024-06-18 17:13 ` dpdklab
2024-06-19 1:16 ` 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=20240618062432.4094958-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).