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