From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw135902 [PATCH] maintainers: updated for Intel drivers
Date: Tue, 16 Jan 2024 22:15:59 -0500 [thread overview]
Message-ID: <20240117031559.3222678-1-robot@bytheb.org> (raw)
In-Reply-To: <20240117101749.257581-1-qiming.yang@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/135902/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7550366144
next prev parent reply other threads:[~2024-01-17 3:16 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240117101749.257581-1-qiming.yang@intel.com>
2024-01-17 2:03 ` qemudev
2024-01-17 2:07 ` qemudev
2024-01-17 2:23 ` checkpatch
2024-01-17 3:15 ` 0-day Robot [this message]
2024-01-18 3:03 dpdklab
2024-01-18 3:04 dpdklab
2024-01-18 3:05 dpdklab
2024-01-18 3:06 dpdklab
2024-01-18 3:07 dpdklab
2024-01-18 3:14 dpdklab
2024-01-18 3:15 dpdklab
2024-01-18 3:18 dpdklab
2024-01-18 3:25 dpdklab
2024-01-18 3:34 dpdklab
2024-01-18 3:38 dpdklab
2024-01-18 3:42 dpdklab
2024-01-18 3:43 dpdklab
2024-01-18 3:45 dpdklab
2024-01-18 3:46 dpdklab
2024-01-18 3:48 dpdklab
2024-01-18 3:51 dpdklab
2024-01-18 3:52 dpdklab
2024-01-18 3:53 dpdklab
2024-01-18 3:55 dpdklab
2024-01-18 3:55 dpdklab
2024-01-18 4:14 dpdklab
2024-01-18 4:15 dpdklab
2024-01-18 4:15 dpdklab
2024-01-18 4:16 dpdklab
2024-01-18 4:24 dpdklab
2024-01-18 4:24 dpdklab
2024-01-18 4:24 dpdklab
2024-01-18 4:26 dpdklab
2024-01-18 4:26 dpdklab
2024-01-18 4:28 dpdklab
2024-01-18 4:29 dpdklab
2024-01-18 4:31 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:37 dpdklab
2024-01-18 4:37 dpdklab
2024-01-18 4:39 dpdklab
2024-01-18 4:39 dpdklab
2024-01-18 4:40 dpdklab
2024-01-18 4:40 dpdklab
2024-01-18 4:42 dpdklab
2024-01-18 4:42 dpdklab
2024-01-18 4:42 dpdklab
2024-01-18 4:43 dpdklab
2024-01-18 4:44 dpdklab
2024-01-18 4:44 dpdklab
2024-01-18 4:44 dpdklab
2024-01-18 4:45 dpdklab
2024-01-18 4:45 dpdklab
2024-01-18 4:48 dpdklab
2024-01-18 4:48 dpdklab
2024-01-18 4:53 dpdklab
2024-01-18 4:54 dpdklab
2024-01-18 4:54 dpdklab
2024-01-18 4:55 dpdklab
2024-01-18 4:55 dpdklab
2024-01-18 4:59 dpdklab
2024-01-18 5:06 dpdklab
2024-01-18 5:14 dpdklab
2024-01-18 5:15 dpdklab
2024-01-18 5:49 dpdklab
2024-01-18 6:00 dpdklab
2024-01-18 6:43 dpdklab
2024-01-18 13:13 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=20240117031559.3222678-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).