From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138487 [PATCH v3] dmadev: fix structure alignment
Date: Wed, 20 Mar 2024 04:23:28 -0400 [thread overview]
Message-ID: <20240320082328.3380501-1-robot@bytheb.org> (raw)
In-Reply-To: <20240320072332.1433526-1-wenwux.ma@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138487/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8355383933
next prev parent reply other threads:[~2024-03-20 8:23 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320072332.1433526-1-wenwux.ma@intel.com>
2024-03-20 7:14 ` qemudev
2024-03-20 7:18 ` qemudev
2024-03-20 7:38 ` checkpatch
2024-03-20 8:17 ` |SUCCESS| pw138487 [PATCH] [v3] " dpdklab
2024-03-20 8:23 ` 0-day Robot [this message]
2024-03-20 8:23 ` dpdklab
2024-03-20 8:37 ` dpdklab
2024-03-20 8:37 ` dpdklab
2024-03-20 8:38 ` dpdklab
2024-03-20 8:38 ` dpdklab
2024-03-20 8:39 ` dpdklab
2024-03-20 8:39 ` dpdklab
2024-03-20 8:40 ` dpdklab
2024-03-20 8:40 ` dpdklab
2024-03-20 8:41 ` dpdklab
2024-03-20 8:41 ` dpdklab
2024-03-20 8:42 ` dpdklab
2024-03-20 8:42 ` dpdklab
2024-03-20 8:42 ` dpdklab
2024-03-20 8:43 ` dpdklab
2024-03-20 8:43 ` dpdklab
2024-03-20 8:43 ` dpdklab
2024-03-20 8:44 ` dpdklab
2024-03-20 8:44 ` dpdklab
2024-03-20 8:45 ` dpdklab
2024-03-20 8:45 ` dpdklab
2024-03-20 8:45 ` dpdklab
2024-03-20 8:45 ` dpdklab
2024-03-20 8:46 ` dpdklab
2024-03-20 8:46 ` dpdklab
2024-03-20 8:46 ` dpdklab
2024-03-20 8:46 ` dpdklab
2024-03-20 8:46 ` dpdklab
2024-03-20 8:47 ` dpdklab
2024-03-20 8:47 ` dpdklab
2024-03-20 8:47 ` dpdklab
2024-03-20 8:47 ` dpdklab
2024-03-20 8:47 ` dpdklab
2024-03-20 8:47 ` dpdklab
2024-03-20 8:48 ` dpdklab
2024-03-20 8:48 ` dpdklab
2024-03-20 8:48 ` dpdklab
2024-03-20 8:48 ` dpdklab
2024-03-20 8:48 ` |FAILURE| " dpdklab
2024-03-20 8:48 ` dpdklab
2024-03-20 8:49 ` dpdklab
2024-03-20 8:49 ` |SUCCESS| " dpdklab
2024-03-20 8:49 ` |FAILURE| " dpdklab
2024-03-20 8:49 ` |SUCCESS| " dpdklab
2024-03-20 8:49 ` |FAILURE| " dpdklab
2024-03-20 8:49 ` |SUCCESS| " dpdklab
2024-03-20 8:50 ` dpdklab
2024-03-20 8:50 ` |FAILURE| " dpdklab
2024-03-20 8:50 ` |SUCCESS| " dpdklab
2024-03-20 8:50 ` |FAILURE| " dpdklab
2024-03-20 8:50 ` |SUCCESS| " dpdklab
2024-03-20 8:50 ` dpdklab
2024-03-20 8:50 ` dpdklab
2024-03-20 8:51 ` |FAILURE| " dpdklab
2024-03-20 8:51 ` dpdklab
2024-03-20 8:51 ` dpdklab
2024-03-20 8:51 ` |SUCCESS| " dpdklab
2024-03-20 8:51 ` dpdklab
2024-03-20 8:51 ` |FAILURE| " dpdklab
2024-03-20 8:52 ` |SUCCESS| " dpdklab
2024-03-20 8:52 ` dpdklab
2024-03-20 8:52 ` dpdklab
2024-03-20 8:52 ` dpdklab
2024-03-20 8:53 ` |FAILURE| " dpdklab
2024-03-20 8:53 ` |SUCCESS| " dpdklab
2024-03-20 8:53 ` dpdklab
2024-03-20 8:53 ` dpdklab
2024-03-20 8:53 ` dpdklab
2024-03-20 8:54 ` dpdklab
2024-03-20 8:54 ` dpdklab
2024-03-20 9:04 ` dpdklab
2024-03-20 9:05 ` |FAILURE| " dpdklab
2024-03-20 9:07 ` |SUCCESS| " dpdklab
2024-03-20 11:30 ` dpdklab
2024-03-21 2:36 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:32 ` 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=20240320082328.3380501-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).