From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141278 [PATCH] net/ring: Set mbuf->port for received packets
Date: Tue, 18 Jun 2024 11:44:31 -0400 [thread overview]
Message-ID: <20240618154431.1277290-1-robot@bytheb.org> (raw)
In-Reply-To: <20240618134700.3709388-1-sriram.yagnaraman@ericsson.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141278/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9567233547
next prev parent reply other threads:[~2024-06-18 15:44 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618134700.3709388-1-sriram.yagnaraman@ericsson.com>
2024-06-18 13:50 ` qemudev
2024-06-18 13:55 ` qemudev
2024-06-18 14:19 ` checkpatch
2024-06-18 15:44 ` 0-day Robot [this message]
2024-06-18 20:19 ` |SUCCESS| pw141278 [PATCH] net/ring: Set mbuf->port for received pac dpdklab
2024-06-18 20:20 ` dpdklab
2024-06-18 20:22 ` dpdklab
2024-06-18 20:25 ` dpdklab
2024-06-18 20:28 ` dpdklab
2024-06-18 20:29 ` dpdklab
2024-06-18 21:30 ` dpdklab
2024-06-18 21:33 ` dpdklab
2024-06-18 21:36 ` dpdklab
2024-06-18 21:37 ` dpdklab
2024-06-18 21:45 ` dpdklab
2024-06-18 21:45 ` dpdklab
2024-06-18 21:48 ` dpdklab
2024-06-18 21:50 ` dpdklab
2024-06-18 21:56 ` dpdklab
2024-06-18 21:56 ` dpdklab
2024-06-18 21:59 ` dpdklab
2024-06-18 22:00 ` dpdklab
2024-06-18 22:02 ` dpdklab
2024-06-18 22:04 ` dpdklab
2024-06-18 22:06 ` dpdklab
2024-06-18 22:07 ` dpdklab
2024-06-18 22:08 ` dpdklab
2024-06-18 22:23 ` dpdklab
2024-06-18 22:24 ` dpdklab
2024-06-18 22:26 ` dpdklab
2024-06-18 22:26 ` dpdklab
2024-06-18 22:32 ` dpdklab
2024-06-18 22:33 ` dpdklab
2024-06-18 22:33 ` dpdklab
2024-06-18 22:34 ` dpdklab
2024-06-18 22:36 ` dpdklab
2024-06-18 23:47 ` dpdklab
2024-06-18 23:48 ` dpdklab
2024-06-18 23:49 ` dpdklab
2024-06-18 23:49 ` dpdklab
2024-06-18 23:49 ` dpdklab
2024-06-19 0:16 ` dpdklab
2024-06-19 0:29 ` dpdklab
2024-06-19 2:36 ` dpdklab
2024-06-19 2:55 ` dpdklab
2024-06-19 2:55 ` dpdklab
2024-06-19 2:57 ` dpdklab
2024-06-19 3:03 ` dpdklab
2024-06-19 3:05 ` dpdklab
2024-06-19 3:06 ` dpdklab
2024-06-19 3:07 ` dpdklab
2024-06-19 3:09 ` dpdklab
2024-06-19 3:13 ` dpdklab
2024-06-19 3:22 ` dpdklab
2024-06-19 3:27 ` dpdklab
2024-06-19 3:29 ` dpdklab
2024-06-19 3:29 ` dpdklab
2024-06-19 3:31 ` dpdklab
2024-06-19 3:32 ` dpdklab
2024-06-19 3:32 ` dpdklab
2024-06-19 3:39 ` dpdklab
2024-06-19 3:41 ` dpdklab
2024-06-19 3:42 ` dpdklab
2024-06-19 3:47 ` dpdklab
2024-06-19 3:49 ` dpdklab
2024-06-19 3:49 ` dpdklab
2024-06-19 3:51 ` dpdklab
2024-06-19 3:55 ` dpdklab
2024-06-19 4:01 ` dpdklab
2024-06-19 4:06 ` dpdklab
2024-06-19 4:21 ` dpdklab
2024-06-19 4:22 ` dpdklab
2024-06-19 4:23 ` dpdklab
2024-06-19 4:23 ` dpdklab
2024-06-19 4:23 ` dpdklab
2024-06-19 4:25 ` dpdklab
2024-06-19 4:25 ` dpdklab
2024-06-19 4:27 ` dpdklab
2024-06-19 4:27 ` dpdklab
2024-06-19 4:28 ` dpdklab
2024-06-19 4:28 ` dpdklab
2024-06-19 4:29 ` dpdklab
2024-06-19 4:31 ` dpdklab
2024-06-19 4:31 ` dpdklab
2024-06-19 4:36 ` 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:26 ` dpdklab
2024-06-19 5:27 ` dpdklab
2024-06-19 5:28 ` dpdklab
2024-06-19 5:30 ` dpdklab
2024-06-19 5:35 ` dpdklab
2024-06-19 5:45 ` dpdklab
2024-06-19 5:47 ` dpdklab
2024-06-19 5:52 ` dpdklab
2024-06-19 5:55 ` dpdklab
2024-06-19 5:59 ` dpdklab
2024-06-19 6:02 ` dpdklab
2024-06-19 6:05 ` dpdklab
2024-06-19 6:07 ` dpdklab
2024-06-19 6:08 ` dpdklab
2024-06-19 6:14 ` dpdklab
2024-06-19 6:15 ` dpdklab
2024-06-19 6:17 ` dpdklab
2024-06-19 6:21 ` dpdklab
2024-06-19 7:00 ` dpdklab
2024-06-19 7:02 ` dpdklab
2024-06-19 7:03 ` dpdklab
2024-06-19 7:03 ` dpdklab
2024-06-19 7:04 ` dpdklab
2024-06-19 7:07 ` dpdklab
2024-06-19 7:12 ` dpdklab
2024-06-19 14:12 ` dpdklab
2024-06-19 14:30 ` dpdklab
2024-06-20 14:27 ` 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=20240618154431.1277290-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).