From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138410 [PATCH v2] dmadev: fix structure alignment
Date: Fri, 15 Mar 2024 00:23:29 -0400 [thread overview]
Message-ID: <20240315042329.2650622-1-robot@bytheb.org> (raw)
In-Reply-To: <20240315014331.1376720-1-wenwux.ma@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138410/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8291006109
next prev parent reply other threads:[~2024-03-15 4:23 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315014331.1376720-1-wenwux.ma@intel.com>
2024-03-15 1:33 ` qemudev
2024-03-15 1:38 ` qemudev
2024-03-15 1:57 ` checkpatch
2024-03-15 3:59 ` |SUCCESS| pw138410 [PATCH] [v2] " dpdklab
2024-03-15 3:59 ` dpdklab
2024-03-15 4:16 ` dpdklab
2024-03-15 4:17 ` dpdklab
2024-03-15 4:18 ` dpdklab
2024-03-15 4:18 ` dpdklab
2024-03-15 4:18 ` dpdklab
2024-03-15 4:19 ` dpdklab
2024-03-15 4:19 ` dpdklab
2024-03-15 4:19 ` dpdklab
2024-03-15 4:19 ` dpdklab
2024-03-15 4:20 ` dpdklab
2024-03-15 4:20 ` dpdklab
2024-03-15 4:23 ` 0-day Robot [this message]
2024-03-15 4:23 ` dpdklab
2024-03-15 4:23 ` dpdklab
2024-03-15 4:25 ` dpdklab
2024-03-15 4:27 ` dpdklab
2024-03-15 4:27 ` dpdklab
2024-03-15 4:27 ` dpdklab
2024-03-15 4:28 ` dpdklab
2024-03-15 4:28 ` dpdklab
2024-03-15 4:28 ` dpdklab
2024-03-15 4:28 ` dpdklab
2024-03-15 4:28 ` dpdklab
2024-03-15 4:28 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:29 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:30 ` dpdklab
2024-03-15 4:31 ` dpdklab
2024-03-15 4:31 ` dpdklab
2024-03-15 4:31 ` dpdklab
2024-03-15 4:31 ` dpdklab
2024-03-15 4:32 ` dpdklab
2024-03-15 4:32 ` dpdklab
2024-03-15 4:32 ` dpdklab
2024-03-15 4:32 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:33 ` dpdklab
2024-03-15 4:34 ` dpdklab
2024-03-15 4:34 ` dpdklab
2024-03-15 4:34 ` dpdklab
2024-03-15 4:34 ` dpdklab
2024-03-15 4:34 ` dpdklab
2024-03-15 4:35 ` dpdklab
2024-03-15 4:35 ` dpdklab
2024-03-15 4:35 ` dpdklab
2024-03-15 4:53 ` dpdklab
2024-03-15 4:55 ` dpdklab
2024-03-15 5:04 ` dpdklab
2024-03-15 5:07 ` dpdklab
2024-03-15 5:29 ` dpdklab
2024-03-15 5:45 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:59 ` 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=20240315042329.2650622-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).