From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141274 [PATCH v4 21/21] doc: updated the documentation for cpfl PMD
Date: Tue, 18 Jun 2024 08:44:36 -0400 [thread overview]
Message-ID: <20240618124436.520878-1-robot@bytheb.org> (raw)
In-Reply-To: <20240618105722.2326987-22-soumyadeep.hore@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141274/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9564656167
next prev parent reply other threads:[~2024-06-18 12:44 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618105722.2326987-22-soumyadeep.hore@intel.com>
2024-06-18 11:21 ` |SUCCESS| pw141254-141274 " qemudev
2024-06-18 11:26 ` qemudev
2024-06-18 11:47 ` |SUCCESS| pw141274 " checkpatch
2024-06-18 12:44 ` 0-day Robot [this message]
2024-06-18 13:48 ` |SUCCESS| pw141254-141274 [PATCH] [v4,21/21] doc: updated the docume dpdklab
2024-06-18 13:57 ` dpdklab
2024-06-18 13:58 ` dpdklab
2024-06-18 13:59 ` dpdklab
2024-06-18 13:59 ` dpdklab
2024-06-18 14:00 ` dpdklab
2024-06-18 14:00 ` dpdklab
2024-06-18 14:01 ` dpdklab
2024-06-18 14:01 ` dpdklab
2024-06-18 14:02 ` dpdklab
2024-06-18 14:04 ` dpdklab
2024-06-18 14:07 ` dpdklab
2024-06-18 14:08 ` dpdklab
2024-06-18 14:10 ` dpdklab
2024-06-18 14:13 ` dpdklab
2024-06-18 14:14 ` dpdklab
2024-06-18 15:00 ` dpdklab
2024-06-18 15:01 ` dpdklab
2024-06-18 15:02 ` dpdklab
2024-06-18 15:02 ` dpdklab
2024-06-18 15:03 ` dpdklab
2024-06-18 15:04 ` dpdklab
2024-06-18 15:04 ` dpdklab
2024-06-18 15:05 ` dpdklab
2024-06-18 15:05 ` dpdklab
2024-06-18 15:05 ` dpdklab
2024-06-18 15:06 ` dpdklab
2024-06-18 15:06 ` dpdklab
2024-06-18 15:07 ` dpdklab
2024-06-18 15:10 ` dpdklab
2024-06-18 15:35 ` dpdklab
2024-06-18 15:35 ` dpdklab
2024-06-18 15:36 ` dpdklab
2024-06-18 15:38 ` dpdklab
2024-06-18 15:38 ` dpdklab
2024-06-18 15:41 ` dpdklab
2024-06-18 15:42 ` dpdklab
2024-06-18 15:42 ` dpdklab
2024-06-18 15:43 ` dpdklab
2024-06-18 15:46 ` dpdklab
2024-06-18 16:24 ` dpdklab
2024-06-18 16:27 ` dpdklab
2024-06-18 16:27 ` dpdklab
2024-06-18 16:28 ` dpdklab
2024-06-18 16:51 ` dpdklab
2024-06-18 16:53 ` dpdklab
2024-06-18 16:55 ` dpdklab
2024-06-18 16:58 ` dpdklab
2024-06-18 17:11 ` dpdklab
2024-06-18 17:12 ` dpdklab
2024-06-18 17:14 ` dpdklab
2024-06-18 17:15 ` dpdklab
2024-06-18 17:19 ` dpdklab
2024-06-18 17:19 ` dpdklab
2024-06-18 17:20 ` dpdklab
2024-06-18 17:20 ` dpdklab
2024-06-18 17:23 ` dpdklab
2024-06-18 17:23 ` dpdklab
2024-06-18 17:27 ` dpdklab
2024-06-18 17:29 ` dpdklab
2024-06-18 17:29 ` dpdklab
2024-06-18 17:30 ` dpdklab
2024-06-18 17:33 ` dpdklab
2024-06-18 17:39 ` dpdklab
2024-06-18 17:39 ` dpdklab
2024-06-18 17:42 ` dpdklab
2024-06-18 17:42 ` dpdklab
2024-06-18 17:45 ` dpdklab
2024-06-18 17:46 ` dpdklab
2024-06-18 17:47 ` dpdklab
2024-06-18 17:48 ` dpdklab
2024-06-18 17:48 ` dpdklab
2024-06-18 17:50 ` dpdklab
2024-06-18 17:50 ` dpdklab
2024-06-18 17:55 ` dpdklab
2024-06-18 17:56 ` dpdklab
2024-06-18 17:58 ` dpdklab
2024-06-18 17:58 ` dpdklab
2024-06-18 17:58 ` dpdklab
2024-06-18 17:59 ` dpdklab
2024-06-18 17:59 ` dpdklab
2024-06-18 18:00 ` dpdklab
2024-06-18 18:01 ` dpdklab
2024-06-18 18:01 ` dpdklab
2024-06-18 18:02 ` dpdklab
2024-06-18 18:02 ` dpdklab
2024-06-18 18:03 ` dpdklab
2024-06-18 18:03 ` dpdklab
2024-06-18 18:04 ` dpdklab
2024-06-18 18:08 ` dpdklab
2024-06-18 18:08 ` dpdklab
2024-06-18 18:09 ` dpdklab
2024-06-18 18:09 ` dpdklab
2024-06-18 18:10 ` dpdklab
2024-06-18 18:11 ` dpdklab
2024-06-18 18:11 ` dpdklab
2024-06-18 18:11 ` dpdklab
2024-06-18 18:12 ` dpdklab
2024-06-18 18:12 ` dpdklab
2024-06-18 18:17 ` dpdklab
2024-06-18 18:26 ` dpdklab
2024-06-18 18:27 ` dpdklab
2024-06-18 18:44 ` dpdklab
2024-06-18 19:00 ` dpdklab
2024-06-18 19:02 ` dpdklab
2024-06-18 19:09 ` dpdklab
2024-06-18 20:17 ` dpdklab
2024-06-18 20:20 ` dpdklab
2024-06-19 0:27 ` dpdklab
2024-06-19 2:22 ` dpdklab
2024-06-19 16: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=20240618124436.520878-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).