From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141412 [PATCH v5 5/5] doc: update release notes for 24.07
Date: Wed, 19 Jun 2024 18:05:39 -0400 [thread overview]
Message-ID: <20240619220539.4030436-1-robot@bytheb.org> (raw)
In-Reply-To: <20240619210106.253239-6-abdullah.sevincer@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141412/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9588321735
next prev parent reply other threads:[~2024-06-19 22:05 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240619210106.253239-6-abdullah.sevincer@intel.com>
2024-06-19 20:41 ` |SUCCESS| pw141408-141412 " qemudev
2024-06-19 20:45 ` qemudev
2024-06-19 21:02 ` |SUCCESS| pw141412 " checkpatch
2024-06-19 22:05 ` 0-day Robot [this message]
2024-06-20 0:55 ` |SUCCESS| pw141408-141412 [PATCH] [v5,5/5] doc: update release notes dpdklab
2024-06-20 0:55 ` dpdklab
2024-06-20 0:56 ` dpdklab
2024-06-20 0:58 ` dpdklab
2024-06-20 0:59 ` dpdklab
2024-06-20 1:04 ` dpdklab
2024-06-20 1:05 ` dpdklab
2024-06-20 1:06 ` dpdklab
2024-06-20 1:13 ` dpdklab
2024-06-20 1:21 ` dpdklab
2024-06-20 1:21 ` dpdklab
2024-06-20 1:23 ` dpdklab
2024-06-20 1:26 ` dpdklab
2024-06-20 1:27 ` dpdklab
2024-06-20 1:29 ` dpdklab
2024-06-20 1:48 ` dpdklab
2024-06-20 1:49 ` dpdklab
2024-06-20 1:50 ` dpdklab
2024-06-20 1:51 ` dpdklab
2024-06-20 1:51 ` dpdklab
2024-06-20 1:52 ` dpdklab
2024-06-20 1:52 ` dpdklab
2024-06-20 2:09 ` dpdklab
2024-06-20 2:19 ` dpdklab
2024-06-20 2:21 ` dpdklab
2024-06-20 2:22 ` dpdklab
2024-06-20 2:23 ` dpdklab
2024-06-20 2:27 ` dpdklab
2024-06-20 2:29 ` dpdklab
2024-06-20 2:30 ` dpdklab
2024-06-20 2:30 ` dpdklab
2024-06-20 2:31 ` dpdklab
2024-06-20 2:35 ` dpdklab
2024-06-20 2:36 ` dpdklab
2024-06-20 2:36 ` dpdklab
2024-06-20 2:36 ` dpdklab
2024-06-20 2:37 ` dpdklab
2024-06-20 2:38 ` dpdklab
2024-06-20 2:39 ` dpdklab
2024-06-20 2:59 ` dpdklab
2024-06-20 3:54 ` dpdklab
2024-06-20 3:56 ` dpdklab
2024-06-20 3:58 ` dpdklab
2024-06-20 3:59 ` dpdklab
2024-06-20 3:59 ` dpdklab
2024-06-20 3:59 ` dpdklab
2024-06-20 3:59 ` dpdklab
2024-06-20 4:00 ` dpdklab
2024-06-20 4:00 ` dpdklab
2024-06-20 4:01 ` dpdklab
2024-06-20 4:01 ` dpdklab
2024-06-20 4:01 ` dpdklab
2024-06-20 4:02 ` dpdklab
2024-06-20 4:04 ` dpdklab
2024-06-20 4:05 ` dpdklab
2024-06-20 4:06 ` dpdklab
2024-06-20 4:06 ` dpdklab
2024-06-20 4:23 ` dpdklab
2024-06-20 4:27 ` dpdklab
2024-06-20 4:29 ` dpdklab
2024-06-20 4:29 ` dpdklab
2024-06-20 4:30 ` dpdklab
2024-06-20 4:30 ` dpdklab
2024-06-20 4:30 ` dpdklab
2024-06-20 4:30 ` dpdklab
2024-06-20 4:31 ` dpdklab
2024-06-20 4:31 ` dpdklab
2024-06-20 4:31 ` dpdklab
2024-06-20 4:31 ` dpdklab
2024-06-20 4:31 ` dpdklab
2024-06-20 4:32 ` dpdklab
2024-06-20 4:32 ` dpdklab
2024-06-20 4:35 ` dpdklab
2024-06-20 4:35 ` dpdklab
2024-06-20 4:37 ` dpdklab
2024-06-20 4:38 ` dpdklab
2024-06-20 4:43 ` dpdklab
2024-06-20 4:44 ` dpdklab
2024-06-20 4:45 ` dpdklab
2024-06-20 4:46 ` dpdklab
2024-06-20 4:56 ` dpdklab
2024-06-20 5:05 ` dpdklab
2024-06-20 5:08 ` dpdklab
2024-06-20 5:18 ` dpdklab
2024-06-20 5:20 ` dpdklab
2024-06-20 6:03 ` dpdklab
2024-06-20 6:18 ` dpdklab
2024-06-20 6:24 ` dpdklab
2024-06-20 6:25 ` dpdklab
2024-06-20 6:26 ` dpdklab
2024-06-20 6:38 ` dpdklab
2024-06-20 6:43 ` dpdklab
2024-06-20 6:44 ` dpdklab
2024-06-20 6:53 ` dpdklab
2024-06-20 6:54 ` dpdklab
2024-06-20 7:02 ` dpdklab
2024-06-20 7:13 ` dpdklab
2024-06-20 7:20 ` dpdklab
2024-06-20 7:29 ` dpdklab
2024-06-20 7:29 ` dpdklab
2024-06-20 7:36 ` dpdklab
2024-06-20 7:40 ` dpdklab
2024-06-20 7:55 ` dpdklab
2024-06-20 7:59 ` dpdklab
2024-06-20 8:04 ` dpdklab
2024-06-20 8:34 ` dpdklab
2024-06-20 9:35 ` dpdklab
2024-06-20 9:38 ` dpdklab
2024-06-20 11:00 ` dpdklab
2024-06-20 12:10 ` dpdklab
2024-06-21 22:08 ` 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=20240619220539.4030436-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).