From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143181 [PATCH v17 5/5] dts: add API doc generation
Date: Wed, 14 Aug 2024 12:02:55 -0400 [thread overview]
Message-ID: <20240814160255.3635397-1-robot@bytheb.org> (raw)
In-Reply-To: <20240814150535.239547-6-juraj.linkes@pantheon.tech>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143181/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10390432850
next prev parent reply other threads:[~2024-08-14 16:02 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240814150535.239547-6-juraj.linkes@pantheon.tech>
2024-08-14 14:41 ` |SUCCESS| pw143177-143181 " qemudev
2024-08-14 14:45 ` qemudev
2024-08-14 15:06 ` |WARNING| pw143181 " checkpatch
2024-08-14 15:37 ` |PENDING| pw143177-143181 [PATCH] [v17,5/5] dts: add API doc generat dpdklab
2024-08-14 15:39 ` |SUCCESS| " dpdklab
2024-08-14 15:39 ` |PENDING| " dpdklab
2024-08-14 15:40 ` dpdklab
2024-08-14 15:42 ` |SUCCESS| " dpdklab
2024-08-14 15:42 ` |PENDING| " dpdklab
2024-08-14 15:43 ` dpdklab
2024-08-14 15:43 ` |SUCCESS| " dpdklab
2024-08-14 15:43 ` |PENDING| " dpdklab
2024-08-14 15:44 ` |SUCCESS| " dpdklab
2024-08-14 15:45 ` |PENDING| " dpdklab
2024-08-14 15:46 ` dpdklab
2024-08-14 15:46 ` dpdklab
2024-08-14 15:46 ` dpdklab
2024-08-14 15:47 ` dpdklab
2024-08-14 15:48 ` dpdklab
2024-08-14 15:48 ` dpdklab
2024-08-14 15:49 ` dpdklab
2024-08-14 15:51 ` dpdklab
2024-08-14 15:51 ` dpdklab
2024-08-14 15:51 ` |SUCCESS| " dpdklab
2024-08-14 15:52 ` |PENDING| " dpdklab
2024-08-14 15:53 ` dpdklab
2024-08-14 15:57 ` dpdklab
2024-08-14 16:01 ` dpdklab
2024-08-14 16:02 ` 0-day Robot [this message]
2024-08-14 16:03 ` dpdklab
2024-08-14 16:03 ` dpdklab
2024-08-14 16:04 ` dpdklab
2024-08-14 16:07 ` dpdklab
2024-08-14 16:08 ` dpdklab
2024-08-14 16:10 ` |SUCCESS| " dpdklab
2024-08-14 16:13 ` |PENDING| " dpdklab
2024-08-14 16:15 ` dpdklab
2024-08-14 16:16 ` |SUCCESS| " dpdklab
2024-08-14 16:16 ` |PENDING| " dpdklab
2024-08-14 16:17 ` dpdklab
2024-08-14 16:17 ` dpdklab
2024-08-14 16:18 ` |SUCCESS| " dpdklab
2024-08-14 16:18 ` dpdklab
2024-08-14 16:18 ` |PENDING| " dpdklab
2024-08-14 16:18 ` dpdklab
2024-08-14 16:18 ` dpdklab
2024-08-14 16:19 ` dpdklab
2024-08-14 16:20 ` |SUCCESS| " dpdklab
2024-08-14 16:20 ` |PENDING| " dpdklab
2024-08-14 16:20 ` |SUCCESS| " dpdklab
2024-08-14 16:21 ` |PENDING| " dpdklab
2024-08-14 16:21 ` dpdklab
2024-08-14 16:21 ` |SUCCESS| " dpdklab
2024-08-14 16:21 ` |PENDING| " dpdklab
2024-08-14 16:22 ` dpdklab
2024-08-14 16:22 ` |SUCCESS| " dpdklab
2024-08-14 16:22 ` dpdklab
2024-08-14 16:23 ` dpdklab
2024-08-14 16:23 ` dpdklab
2024-08-14 16:23 ` |PENDING| " dpdklab
2024-08-14 16:23 ` |SUCCESS| " dpdklab
2024-08-14 16:24 ` dpdklab
2024-08-14 16:24 ` |PENDING| " dpdklab
2024-08-14 16:25 ` dpdklab
2024-08-14 16:25 ` dpdklab
2024-08-14 16:25 ` dpdklab
2024-08-14 16:25 ` dpdklab
2024-08-14 16:26 ` |SUCCESS| " dpdklab
2024-08-14 16:26 ` dpdklab
2024-08-14 16:26 ` |PENDING| " dpdklab
2024-08-14 16:26 ` |SUCCESS| " dpdklab
2024-08-14 16:26 ` |PENDING| " dpdklab
2024-08-14 16:26 ` dpdklab
2024-08-14 16:27 ` dpdklab
2024-08-14 16:27 ` dpdklab
2024-08-14 16:27 ` dpdklab
2024-08-14 16:28 ` dpdklab
2024-08-14 16:28 ` dpdklab
2024-08-14 16:28 ` dpdklab
2024-08-14 16:28 ` dpdklab
2024-08-14 16:28 ` dpdklab
2024-08-14 16:29 ` dpdklab
2024-08-14 16:29 ` dpdklab
2024-08-14 16:29 ` dpdklab
2024-08-14 16:29 ` dpdklab
2024-08-14 16:31 ` dpdklab
2024-08-14 16:32 ` dpdklab
2024-08-14 16:33 ` dpdklab
2024-08-14 16:34 ` dpdklab
2024-08-14 16:36 ` |SUCCESS| " dpdklab
2024-08-14 16:39 ` dpdklab
2024-08-14 16:48 ` dpdklab
2024-08-14 17:30 ` |PENDING| " dpdklab
2024-08-14 17:49 ` |SUCCESS| " dpdklab
2024-08-14 17:53 ` 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=20240814160255.3635397-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).