From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw135243 [PATCH] net/e1000: support launchtime feature
Date: Sun, 17 Dec 2023 16:30:29 -0500 [thread overview]
Message-ID: <20231217213029.4005050-1-robot@bytheb.org> (raw)
In-Reply-To: <20231217202040.478959-1-chuanyu.xue@uconn.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/135243/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7240896619
next prev parent reply other threads:[~2023-12-17 21:30 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231217202040.478959-1-chuanyu.xue@uconn.edu>
2023-12-17 20:02 ` qemudev
2023-12-17 20:06 ` qemudev
2023-12-17 20:22 ` |WARNING| " checkpatch
2023-12-17 21:30 ` 0-day Robot [this message]
2023-12-17 22:24 |SUCCESS| " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-12-17 22:04 dpdklab
2023-12-17 21:58 dpdklab
2023-12-17 21:47 dpdklab
2023-12-17 21:47 dpdklab
2023-12-17 21:44 dpdklab
2023-12-17 21:43 dpdklab
2023-12-17 21:43 dpdklab
2023-12-17 21:43 dpdklab
2023-12-17 21:40 dpdklab
2023-12-17 21:39 dpdklab
2023-12-17 21:37 dpdklab
2023-12-17 21:36 dpdklab
2023-12-17 21:35 dpdklab
2023-12-17 21:33 dpdklab
2023-12-17 21:33 dpdklab
2023-12-17 21:32 dpdklab
2023-12-17 21:32 dpdklab
2023-12-17 21:27 dpdklab
2023-12-17 21:26 dpdklab
2023-12-17 21:26 dpdklab
2023-12-17 21:26 dpdklab
2023-12-17 21:25 dpdklab
2023-12-17 21:24 dpdklab
2023-12-17 21:24 dpdklab
2023-12-17 21:23 dpdklab
2023-12-17 21:21 dpdklab
2023-12-17 21:20 dpdklab
2023-12-17 21:19 dpdklab
2023-12-17 21:19 dpdklab
2023-12-17 21:19 dpdklab
2023-12-17 21:18 dpdklab
2023-12-17 21:18 dpdklab
2023-12-17 21:17 dpdklab
2023-12-17 21:17 dpdklab
2023-12-17 21:17 dpdklab
2023-12-17 21:16 dpdklab
2023-12-17 21:16 dpdklab
2023-12-17 21:15 dpdklab
2023-12-17 21:15 dpdklab
2023-12-17 21:15 dpdklab
2023-12-17 21:12 dpdklab
2023-12-17 21:12 dpdklab
2023-12-17 21:12 dpdklab
2023-12-17 21:11 dpdklab
2023-12-17 21:11 dpdklab
2023-12-17 21:10 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:05 dpdklab
2023-12-17 21:05 dpdklab
2023-12-17 21:05 dpdklab
2023-12-17 21:04 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=20231217213029.4005050-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).