From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw135859 [PATCH v1 1/1] baseband/acc: remove acc101
Date: Fri, 12 Jan 2024 16:24:13 -0500 [thread overview]
Message-ID: <20240112212413.3897839-1-robot@bytheb.org> (raw)
In-Reply-To: <20240112203618.27094-2-hernan.vargas@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/135859/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7507301663
next prev parent reply other threads:[~2024-01-12 21:24 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240112203618.27094-2-hernan.vargas@intel.com>
2024-01-12 20:39 ` checkpatch
2024-01-12 21:24 ` 0-day Robot [this message]
2024-01-15 5:43 ` qemudev
2024-01-15 5:47 ` |FAILURE| " qemudev
2024-01-15 6:58 ` |SUCCESS| " qemudev
2024-01-15 7:02 ` qemudev
2024-01-17 4:33 |SUCCESS| pw135859 [PATCH] [v1,1/1] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-01-15 0:55 dpdklab
2024-01-15 0:46 dpdklab
2024-01-15 0:35 dpdklab
2024-01-15 0:34 dpdklab
2024-01-15 0:29 dpdklab
2024-01-15 0:19 dpdklab
2024-01-15 0:19 dpdklab
2024-01-15 0:18 dpdklab
2024-01-15 0:17 dpdklab
2024-01-15 0:16 dpdklab
2024-01-15 0:15 dpdklab
2024-01-15 0:14 dpdklab
2024-01-15 0:14 dpdklab
2024-01-15 0:12 dpdklab
2024-01-15 0:11 dpdklab
2024-01-15 0:11 dpdklab
2024-01-15 0:11 dpdklab
2024-01-15 0:09 dpdklab
2024-01-15 0:07 dpdklab
2024-01-15 0:05 dpdklab
2024-01-15 0:05 dpdklab
2024-01-15 0:04 dpdklab
2024-01-15 0:03 dpdklab
2024-01-15 0:02 dpdklab
2024-01-15 0:01 dpdklab
2024-01-15 0:00 dpdklab
2024-01-14 23:59 dpdklab
2024-01-14 23:55 dpdklab
2024-01-14 23:55 dpdklab
2024-01-14 23:54 dpdklab
2024-01-14 23:53 dpdklab
2024-01-14 23:53 dpdklab
2024-01-14 23:52 dpdklab
2024-01-14 23:49 dpdklab
2024-01-14 23:49 dpdklab
2024-01-14 23:46 dpdklab
2024-01-14 23:46 dpdklab
2024-01-14 23:45 dpdklab
2024-01-14 23:44 dpdklab
2024-01-14 23:44 dpdklab
2024-01-14 23:44 dpdklab
2024-01-14 23:44 dpdklab
2024-01-14 23:43 dpdklab
2024-01-14 23:43 dpdklab
2024-01-14 23:43 dpdklab
2024-01-14 23:42 dpdklab
2024-01-14 23:41 dpdklab
2024-01-14 23:41 dpdklab
2024-01-14 23:41 dpdklab
2024-01-14 23:41 dpdklab
2024-01-14 23:40 dpdklab
2024-01-14 23:38 dpdklab
2024-01-14 23:36 dpdklab
2024-01-14 23:36 dpdklab
2024-01-14 23:35 dpdklab
2024-01-14 23:34 dpdklab
2024-01-14 23:34 dpdklab
2024-01-14 23:33 dpdklab
2024-01-14 23:32 dpdklab
2024-01-14 23:32 dpdklab
2024-01-14 23:31 dpdklab
2024-01-14 23:24 dpdklab
2024-01-14 23:20 dpdklab
2024-01-14 23:16 dpdklab
2024-01-14 23:15 dpdklab
2024-01-14 23:14 dpdklab
2024-01-14 23:00 dpdklab
2024-01-14 23:00 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=20240112212413.3897839-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).