automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw139413 [PATCH v4 16/16] crypto/mlx5: pack structures when building with MSVC
Date: Mon, 15 Apr 2024 21:04:34 -0400	[thread overview]
Message-ID: <20240416010434.3247464-1-robot@bytheb.org> (raw)
In-Reply-To: <1713225913-20792-17-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/139413/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8697961858

  parent reply	other threads:[~2024-04-16  1:04 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1713225913-20792-17-git-send-email-roretzla@linux.microsoft.com>
2024-04-15 23:45 ` |SUCCESS| pw139398-139413 " qemudev
2024-04-15 23:50 ` qemudev
2024-04-16  0:08 ` |SUCCESS| pw139413 " checkpatch
2024-04-16  1:04 ` 0-day Robot [this message]
2024-04-16  9:47 ` |SUCCESS| pw139398-139413 [PATCH] [v4,16/16] crypto/mlx5: pack struc dpdklab
2024-04-16  9:48 ` dpdklab
2024-04-16  9:48 ` dpdklab
2024-04-16  9:52 ` dpdklab
2024-04-16  9:54 ` dpdklab
2024-04-16  9:55 ` dpdklab
2024-04-16  9:56 ` dpdklab
2024-04-16  9:59 ` dpdklab
2024-04-16 10:00 ` dpdklab
2024-04-16 10:01 ` dpdklab
2024-04-16 10:01 ` dpdklab
2024-04-16 10:01 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:03 ` dpdklab
2024-04-16 10:03 ` dpdklab
2024-04-16 10:22 ` dpdklab
2024-04-16 10:29 ` dpdklab
2024-04-16 10:29 ` dpdklab
2024-04-16 10:30 ` dpdklab
2024-04-16 10:30 ` dpdklab
2024-04-16 10:31 ` dpdklab
2024-04-16 10:43 ` dpdklab
2024-04-16 10:44 ` dpdklab
2024-04-16 10:48 ` dpdklab
2024-04-16 10:49 ` dpdklab
2024-04-16 10:49 ` dpdklab
2024-04-16 10:50 ` dpdklab
2024-04-16 10:50 ` dpdklab
2024-04-16 10:52 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:54 ` dpdklab
2024-04-16 10:54 ` dpdklab
2024-04-16 10:54 ` dpdklab
2024-04-16 10:55 ` dpdklab
2024-04-16 10:55 ` dpdklab
2024-04-16 10:55 ` dpdklab
2024-04-16 10:56 ` dpdklab
2024-04-16 10:56 ` dpdklab
2024-04-16 10:56 ` dpdklab
2024-04-16 10:56 ` dpdklab
2024-04-16 10:56 ` dpdklab
2024-04-16 10:57 ` dpdklab
2024-04-16 10:57 ` dpdklab
2024-04-16 10:57 ` dpdklab
2024-04-16 10:57 ` dpdklab
2024-04-16 10:57 ` dpdklab
2024-04-16 10:57 ` dpdklab
2024-04-16 10:58 ` dpdklab
2024-04-16 10:58 ` dpdklab
2024-04-16 10:58 ` dpdklab
2024-04-16 10:58 ` dpdklab
2024-04-16 10:59 ` dpdklab
2024-04-16 10:59 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:01 ` dpdklab
2024-04-16 11:01 ` dpdklab
2024-04-16 11:01 ` dpdklab
2024-04-16 11:02 ` dpdklab
2024-04-16 11:03 ` dpdklab
2024-04-16 11:04 ` dpdklab
2024-04-16 11:06 ` dpdklab
2024-04-16 11:09 ` dpdklab
2024-04-16 11:09 ` dpdklab
2024-04-16 11:10 ` dpdklab
2024-04-16 11:11 ` dpdklab
2024-04-16 11:13 ` dpdklab
2024-04-16 11:14 ` dpdklab
2024-04-16 11:19 ` dpdklab
2024-04-16 11:31 ` dpdklab
2024-04-16 11:35 ` dpdklab
2024-04-16 11:38 ` dpdklab
2024-04-16 11:41 ` dpdklab
2024-04-16 11:42 ` dpdklab
2024-04-16 11:50 ` dpdklab
2024-04-16 11:54 ` dpdklab
2024-04-16 11:56 ` dpdklab
2024-04-16 12:11 ` dpdklab
2024-04-16 12:18 ` dpdklab
2024-04-16 12:21 ` dpdklab
2024-04-16 12:28 ` dpdklab
2024-04-16 14:17 ` dpdklab
2024-04-16 14:19 ` dpdklab
2024-04-16 14:29 ` 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=20240416010434.3247464-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).