From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw130164 [PATCH] build: move AVX512 check to x86 config
Date: Fri, 11 Aug 2023 10:19:14 -0400 [thread overview]
Message-ID: <20230811141914.4152422-1-robot@bytheb.org> (raw)
In-Reply-To: <20230811131024.2285366-1-david.marchand@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/130164/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5833087600
next prev parent reply other threads:[~2023-08-11 14:19 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230811131024.2285366-1-david.marchand@redhat.com>
2023-08-11 13:01 ` qemudev
2023-08-11 13:05 ` qemudev
2023-08-11 13:11 ` checkpatch
2023-08-11 14:19 ` 0-day Robot [this message]
2023-08-11 15:32 dpdklab
2023-08-11 15:33 dpdklab
2023-08-11 15:36 dpdklab
2023-08-11 15:37 dpdklab
2023-08-11 15:49 dpdklab
2023-08-11 15:55 dpdklab
2023-08-11 15:56 dpdklab
2023-08-11 15:56 dpdklab
2023-08-11 15:58 dpdklab
2023-08-11 15:59 dpdklab
2023-08-11 16:01 dpdklab
2023-08-11 16:01 dpdklab
2023-08-11 16:02 dpdklab
2023-08-11 16:02 dpdklab
2023-08-11 16:03 dpdklab
2023-08-11 16:18 dpdklab
2023-08-11 16:23 dpdklab
2023-08-11 16:25 dpdklab
2023-08-11 16:29 dpdklab
2023-08-11 16:31 dpdklab
2023-08-11 16:31 dpdklab
2023-08-11 16:33 dpdklab
2023-08-11 16:37 dpdklab
2023-08-11 16:38 dpdklab
2023-08-11 16:38 dpdklab
2023-08-11 16:38 dpdklab
2023-08-11 16:39 dpdklab
2023-08-11 16:41 dpdklab
2023-08-11 16:44 dpdklab
2023-08-11 16:46 dpdklab
2023-08-11 16:47 dpdklab
2023-08-11 16:52 dpdklab
2023-08-11 17:26 dpdklab
2023-08-11 17:33 dpdklab
2023-08-11 17:42 dpdklab
2023-08-11 17:52 dpdklab
2023-08-11 18:00 dpdklab
2023-08-11 18:03 dpdklab
2023-08-11 18:04 dpdklab
2023-08-11 18:07 dpdklab
2023-08-11 18:11 dpdklab
2023-08-11 18:11 dpdklab
2023-08-11 18:14 dpdklab
2023-08-11 18:15 dpdklab
2023-08-11 18:15 dpdklab
2023-08-11 18:19 dpdklab
2023-08-11 18:19 dpdklab
2023-08-11 18:20 dpdklab
2023-08-12 1:04 dpdklab
2023-08-12 1:06 dpdklab
2023-08-12 1:12 dpdklab
2023-08-12 1:13 dpdklab
2023-08-12 1:16 dpdklab
2023-08-12 1:19 dpdklab
2023-08-12 1:24 dpdklab
2023-08-12 1:27 dpdklab
2023-08-12 1:28 dpdklab
2023-08-12 2:40 dpdklab
2023-08-12 10:00 dpdklab
2023-08-12 10:16 dpdklab
2023-08-12 10:20 dpdklab
2023-08-12 10:25 dpdklab
2023-08-12 10:30 dpdklab
2023-08-12 10:47 dpdklab
2023-08-13 19:02 dpdklab
2023-08-13 20:36 dpdklab
2023-08-13 22:34 dpdklab
2023-08-13 22:35 dpdklab
2023-08-13 22:36 dpdklab
2023-08-13 22:36 dpdklab
2023-08-13 22:39 dpdklab
2023-08-13 22:43 dpdklab
2023-08-13 22:47 dpdklab
2023-08-13 22:50 dpdklab
2023-08-13 22:54 dpdklab
2023-08-13 22:58 dpdklab
2023-08-13 23:01 dpdklab
2023-08-13 23:16 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=20230811141914.4152422-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).