From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141579 [PATCH v7 4/4] dts: add API doc generation
Date: Mon, 24 Jun 2024 11:44:22 -0400 [thread overview]
Message-ID: <20240624154422.4084377-1-robot@bytheb.org> (raw)
In-Reply-To: <20240624142544.35644-5-juraj.linkes@pantheon.tech>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141579/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9647458810
next prev parent reply other threads:[~2024-06-24 15:44 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624142544.35644-5-juraj.linkes@pantheon.tech>
2024-06-24 13:59 ` |SUCCESS| pw141576-141579 " qemudev
2024-06-24 14:04 ` qemudev
2024-06-24 14:28 ` |WARNING| pw141579 " checkpatch
2024-06-24 15:44 ` 0-day Robot [this message]
2024-06-25 2:45 ` |SUCCESS| pw141576-141579 [PATCH] [v7,4/4] dts: add API doc generati dpdklab
2024-06-25 2:46 ` dpdklab
2024-06-25 2:48 ` dpdklab
2024-06-25 3:22 ` dpdklab
2024-06-25 3:22 ` dpdklab
2024-06-25 3:22 ` dpdklab
2024-06-25 3:25 ` dpdklab
2024-06-25 3:26 ` dpdklab
2024-06-25 3:27 ` dpdklab
2024-06-25 3:27 ` dpdklab
2024-06-25 3:28 ` dpdklab
2024-06-25 3:29 ` dpdklab
2024-06-25 3:32 ` dpdklab
2024-06-25 3:33 ` dpdklab
2024-06-25 3:34 ` dpdklab
2024-06-25 3:34 ` dpdklab
2024-06-25 3:35 ` dpdklab
2024-06-25 3:36 ` dpdklab
2024-06-25 3:38 ` dpdklab
2024-06-25 3:39 ` dpdklab
2024-06-25 3:39 ` dpdklab
2024-06-25 3:39 ` dpdklab
2024-06-25 3:41 ` dpdklab
2024-06-25 3:42 ` dpdklab
2024-06-25 3:43 ` dpdklab
2024-06-25 3:43 ` dpdklab
2024-06-25 3:44 ` dpdklab
2024-06-25 3:45 ` dpdklab
2024-06-25 3:45 ` dpdklab
2024-06-25 3:47 ` dpdklab
2024-06-25 3:52 ` dpdklab
2024-06-25 4:29 ` dpdklab
2024-06-25 4:30 ` dpdklab
2024-06-25 4:30 ` dpdklab
2024-06-25 4:31 ` dpdklab
2024-06-25 5:02 ` dpdklab
2024-06-25 5:03 ` dpdklab
2024-06-25 5:05 ` dpdklab
2024-06-25 5:20 ` dpdklab
2024-06-25 6:14 ` dpdklab
2024-06-25 6:47 ` dpdklab
2024-06-25 7:01 ` dpdklab
2024-06-25 7:03 ` dpdklab
2024-06-25 7:07 ` dpdklab
2024-06-25 7:09 ` dpdklab
2024-06-25 7:32 ` dpdklab
2024-06-25 7:36 ` dpdklab
2024-06-25 7:42 ` dpdklab
2024-06-25 7:43 ` dpdklab
2024-06-25 7:47 ` dpdklab
2024-06-25 8:01 ` dpdklab
2024-06-25 8:02 ` dpdklab
2024-06-25 8:09 ` dpdklab
2024-06-25 8:10 ` dpdklab
2024-06-25 8:13 ` dpdklab
2024-06-25 8:15 ` dpdklab
2024-06-25 8:19 ` dpdklab
2024-06-25 8:20 ` dpdklab
2024-06-25 8:23 ` dpdklab
2024-06-25 8:32 ` dpdklab
2024-06-25 8:33 ` dpdklab
2024-06-25 8:39 ` dpdklab
2024-06-25 8:40 ` dpdklab
2024-06-25 8:42 ` dpdklab
2024-06-25 8:46 ` dpdklab
2024-06-25 8:51 ` dpdklab
2024-06-25 8:52 ` dpdklab
2024-06-25 8:57 ` dpdklab
2024-06-25 8:59 ` dpdklab
2024-06-25 9:01 ` dpdklab
2024-06-25 9:04 ` dpdklab
2024-06-25 9:05 ` dpdklab
2024-06-25 9:06 ` dpdklab
2024-06-25 9:06 ` dpdklab
2024-06-25 9:07 ` dpdklab
2024-06-25 9:08 ` dpdklab
2024-06-25 9:09 ` dpdklab
2024-06-25 9:16 ` dpdklab
2024-06-25 9:16 ` dpdklab
2024-06-25 9:17 ` dpdklab
2024-06-25 9:18 ` dpdklab
2024-06-25 9:24 ` dpdklab
2024-06-25 9:25 ` dpdklab
2024-06-25 9:25 ` dpdklab
2024-06-25 9:26 ` dpdklab
2024-06-25 9:27 ` dpdklab
2024-06-25 9:28 ` dpdklab
2024-06-25 9:29 ` dpdklab
2024-06-25 9:30 ` dpdklab
2024-06-25 9:31 ` dpdklab
2024-06-25 9:32 ` dpdklab
2024-06-25 9:33 ` dpdklab
2024-06-25 9:34 ` dpdklab
2024-06-25 9:35 ` dpdklab
2024-06-25 9:35 ` dpdklab
2024-06-25 9:35 ` dpdklab
2024-06-25 9:35 ` dpdklab
2024-06-25 9:37 ` dpdklab
2024-06-25 9:37 ` dpdklab
2024-06-25 9:38 ` dpdklab
2024-06-25 9:40 ` dpdklab
2024-06-25 9:41 ` dpdklab
2024-06-25 9:43 ` dpdklab
2024-06-25 9:50 ` dpdklab
2024-06-25 9:51 ` dpdklab
2024-06-25 9:51 ` dpdklab
2024-06-25 9:54 ` dpdklab
2024-06-25 10:02 ` dpdklab
2024-06-25 10:21 ` dpdklab
2024-06-25 10:26 ` dpdklab
2024-06-25 11:55 ` dpdklab
2024-06-25 13:54 ` dpdklab
2024-06-25 14:57 ` 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=20240624154422.4084377-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).