From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw130094 [PATCH] graph: mark API's as stable
Date: Thu, 10 Aug 2023 14:58:49 -0400 [thread overview]
Message-ID: <20230810185849.3044081-1-robot@bytheb.org> (raw)
In-Reply-To: <20230810180515.113700-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/130094/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5824688131
next prev parent reply other threads:[~2023-08-10 18:58 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230810180515.113700-1-stephen@networkplumber.org>
2023-08-10 18:06 ` checkpatch
2023-08-10 18:58 ` 0-day Robot [this message]
2023-08-10 22:53 ` qemudev
2023-08-10 22:57 ` qemudev
2023-08-14 3:40 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 3:33 dpdklab
2023-08-14 3:30 dpdklab
2023-08-14 3:30 dpdklab
2023-08-14 3:30 dpdklab
2023-08-14 3:29 dpdklab
2023-08-14 3:29 dpdklab
2023-08-14 3:27 dpdklab
2023-08-14 3:27 dpdklab
2023-08-14 3:26 dpdklab
2023-08-14 3:25 dpdklab
2023-08-14 0:07 dpdklab
2023-08-13 19:31 dpdklab
2023-08-11 20:50 dpdklab
2023-08-11 18:37 dpdklab
2023-08-11 18:33 dpdklab
2023-08-11 18:17 dpdklab
2023-08-11 18:12 dpdklab
2023-08-11 13:41 dpdklab
2023-08-11 6:25 dpdklab
2023-08-11 0:30 dpdklab
2023-08-10 23:57 dpdklab
2023-08-10 23:57 dpdklab
2023-08-10 23:55 dpdklab
2023-08-10 23:53 dpdklab
2023-08-10 23:51 dpdklab
2023-08-10 23:49 dpdklab
2023-08-10 23:48 dpdklab
2023-08-10 23:47 dpdklab
2023-08-10 23:45 dpdklab
2023-08-10 23:44 dpdklab
2023-08-10 23:43 dpdklab
2023-08-10 23:33 dpdklab
2023-08-10 23:21 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:09 dpdklab
2023-08-10 23:09 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:07 dpdklab
2023-08-10 23:05 dpdklab
2023-08-10 22:56 dpdklab
2023-08-10 22:48 dpdklab
2023-08-10 22:48 dpdklab
2023-08-10 22:46 dpdklab
2023-08-10 22:46 dpdklab
2023-08-10 22:44 dpdklab
2023-08-10 22:44 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:41 dpdklab
2023-08-10 22:40 dpdklab
2023-08-10 22:40 dpdklab
2023-08-10 22:39 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 21:42 dpdklab
2023-08-10 20:39 dpdklab
2023-08-10 20:38 dpdklab
2023-08-10 20:33 dpdklab
2023-08-10 20:30 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=20230810185849.3044081-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).