From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw136580 [PATCH v2] dmadev: standardize alignment
Date: Sat, 10 Feb 2024 02:28:11 -0500 [thread overview]
Message-ID: <20240210072811.645570-1-robot@bytheb.org> (raw)
In-Reply-To: <20240210062758.1510-1-pbhagavatula@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/136580/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7853273348
next prev parent reply other threads:[~2024-02-10 7:28 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240210062758.1510-1-pbhagavatula@marvell.com>
2024-02-10 6:04 ` qemudev
2024-02-10 6:09 ` qemudev
2024-02-10 6:29 ` checkpatch
2024-02-10 7:28 ` 0-day Robot [this message]
2024-02-10 10:16 |SUCCESS| pw136580 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-10 10:05 dpdklab
2024-02-10 9:48 dpdklab
2024-02-10 9:31 dpdklab
2024-02-10 9:29 dpdklab
2024-02-10 8:30 dpdklab
2024-02-10 8:25 dpdklab
2024-02-10 8:05 dpdklab
2024-02-10 7:58 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:53 dpdklab
2024-02-10 7:53 dpdklab
2024-02-10 7:52 dpdklab
2024-02-10 7:51 dpdklab
2024-02-10 7:51 dpdklab
2024-02-10 7:49 dpdklab
2024-02-10 7:48 dpdklab
2024-02-10 7:47 dpdklab
2024-02-10 7:47 dpdklab
2024-02-10 7:33 dpdklab
2024-02-10 7:32 dpdklab
2024-02-10 7:32 dpdklab
2024-02-10 7:32 dpdklab
2024-02-10 7:32 dpdklab
2024-02-10 7:31 dpdklab
2024-02-10 7:31 dpdklab
2024-02-10 7:29 dpdklab
2024-02-10 7:29 dpdklab
2024-02-10 7:29 dpdklab
2024-02-10 7:28 dpdklab
2024-02-10 7:28 dpdklab
2024-02-10 7:28 dpdklab
2024-02-10 7:28 dpdklab
2024-02-10 7:28 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:26 dpdklab
2024-02-10 7:26 dpdklab
2024-02-10 7:25 dpdklab
2024-02-10 7:25 dpdklab
2024-02-10 7:25 dpdklab
2024-02-10 7:25 dpdklab
2024-02-10 7:25 dpdklab
2024-02-10 7:25 dpdklab
2024-02-10 7:24 dpdklab
2024-02-10 7:22 dpdklab
2024-02-10 7:22 dpdklab
2024-02-10 7:21 dpdklab
2024-02-10 7:21 dpdklab
2024-02-10 7:21 dpdklab
2024-02-10 7:21 dpdklab
2024-02-10 7:21 dpdklab
2024-02-10 7:20 dpdklab
2024-02-10 7:20 dpdklab
2024-02-10 7:20 dpdklab
2024-02-10 7:19 dpdklab
2024-02-10 7:13 dpdklab
2024-02-10 7:13 dpdklab
2024-02-10 7:12 dpdklab
2024-02-10 7:12 dpdklab
2024-02-10 7:12 dpdklab
2024-02-10 7:11 dpdklab
2024-02-10 7:11 dpdklab
2024-02-10 7:11 dpdklab
2024-02-10 7:10 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=20240210072811.645570-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).