From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141994 [PATCH] dpdk-devbind: fix indentation
Date: Mon, 1 Jul 2024 14:45:25 -0400 [thread overview]
Message-ID: <20240701184525.1164582-1-robot@bytheb.org> (raw)
In-Reply-To: <20240701174544.16967-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141994/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9749003382
next prev parent reply other threads:[~2024-07-01 18:45 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701174544.16967-1-stephen@networkplumber.org>
2024-07-01 17:18 ` qemudev
2024-07-01 17:23 ` qemudev
2024-07-01 17:46 ` checkpatch
2024-07-01 18:45 ` 0-day Robot [this message]
2024-07-01 19:26 ` dpdklab
2024-07-01 19:29 ` dpdklab
2024-07-01 19:31 ` dpdklab
2024-07-01 19:32 ` dpdklab
2024-07-01 19:33 ` dpdklab
2024-07-01 19:49 ` |PENDING| " dpdklab
2024-07-01 19:50 ` |SUCCESS| " dpdklab
2024-07-01 19:54 ` dpdklab
2024-07-01 19:55 ` dpdklab
2024-07-01 19:57 ` |PENDING| " dpdklab
2024-07-01 19:59 ` dpdklab
2024-07-01 20:00 ` dpdklab
2024-07-01 20:01 ` dpdklab
2024-07-01 20:02 ` dpdklab
2024-07-01 20:02 ` dpdklab
2024-07-01 20:04 ` dpdklab
2024-07-01 20:04 ` |SUCCESS| " dpdklab
2024-07-01 20:06 ` |PENDING| " dpdklab
2024-07-01 20:07 ` dpdklab
2024-07-01 20:08 ` |SUCCESS| " dpdklab
2024-07-01 20:09 ` dpdklab
2024-07-01 20:09 ` |PENDING| " dpdklab
2024-07-01 20:09 ` |SUCCESS| " dpdklab
2024-07-01 20:10 ` |PENDING| " dpdklab
2024-07-01 20:12 ` dpdklab
2024-07-01 20:13 ` dpdklab
2024-07-01 20:16 ` dpdklab
2024-07-01 20:16 ` dpdklab
2024-07-01 20:16 ` dpdklab
2024-07-01 20:16 ` dpdklab
2024-07-01 20:19 ` dpdklab
2024-07-01 20:20 ` dpdklab
2024-07-01 20:21 ` dpdklab
2024-07-01 20:23 ` dpdklab
2024-07-01 20:23 ` dpdklab
2024-07-01 20:24 ` dpdklab
2024-07-01 20:24 ` dpdklab
2024-07-01 20:25 ` dpdklab
2024-07-01 20:27 ` dpdklab
2024-07-01 20:29 ` dpdklab
2024-07-01 20:32 ` dpdklab
2024-07-01 20:33 ` dpdklab
2024-07-01 20:33 ` dpdklab
2024-07-01 20:33 ` dpdklab
2024-07-01 20:34 ` dpdklab
2024-07-01 20:37 ` dpdklab
2024-07-01 20:38 ` dpdklab
2024-07-01 20:38 ` dpdklab
2024-07-01 20:40 ` dpdklab
2024-07-01 20:41 ` dpdklab
2024-07-01 20:41 ` dpdklab
2024-07-01 20:42 ` dpdklab
2024-07-01 20:42 ` |SUCCESS| " dpdklab
2024-07-01 20:44 ` |PENDING| " dpdklab
2024-07-01 20:47 ` dpdklab
2024-07-01 20:49 ` dpdklab
2024-07-01 20:49 ` dpdklab
2024-07-01 20:50 ` dpdklab
2024-07-01 20:50 ` dpdklab
2024-07-01 20:56 ` dpdklab
2024-07-01 20:57 ` dpdklab
2024-07-01 20:57 ` dpdklab
2024-07-01 21:01 ` |SUCCESS| " dpdklab
2024-07-01 21:03 ` |PENDING| " dpdklab
2024-07-01 21:19 ` dpdklab
2024-07-01 21:21 ` dpdklab
2024-07-01 21:23 ` dpdklab
2024-07-01 21:26 ` dpdklab
2024-07-01 21:26 ` dpdklab
2024-07-01 21:27 ` dpdklab
2024-07-01 21:27 ` dpdklab
2024-07-01 21:28 ` dpdklab
2024-07-01 21:30 ` dpdklab
2024-07-01 21:31 ` dpdklab
2024-07-01 21:36 ` dpdklab
2024-07-01 21:36 ` dpdklab
2024-07-01 21:36 ` dpdklab
2024-07-01 21:40 ` dpdklab
2024-07-01 21:40 ` dpdklab
2024-07-01 21:41 ` dpdklab
2024-07-01 21:43 ` dpdklab
2024-07-01 21:43 ` dpdklab
2024-07-01 21:44 ` dpdklab
2024-07-01 21:46 ` dpdklab
2024-07-01 21:47 ` dpdklab
2024-07-01 21:49 ` dpdklab
2024-07-01 21:50 ` dpdklab
2024-07-01 21:51 ` dpdklab
2024-07-01 21:51 ` dpdklab
2024-07-01 21:54 ` dpdklab
2024-07-01 21:54 ` dpdklab
2024-07-01 21:55 ` dpdklab
2024-07-01 21:57 ` dpdklab
2024-07-01 21:58 ` |SUCCESS| " dpdklab
2024-07-01 21:58 ` |PENDING| " dpdklab
2024-07-01 21:59 ` |SUCCESS| " dpdklab
2024-07-01 21:59 ` |PENDING| " dpdklab
2024-07-01 21:59 ` dpdklab
2024-07-01 21:59 ` |SUCCESS| " dpdklab
2024-07-01 22:01 ` dpdklab
2024-07-01 22:18 ` |PENDING| " dpdklab
2024-07-01 22:24 ` dpdklab
2024-07-01 22:28 ` |SUCCESS| " dpdklab
2024-07-02 13:31 ` dpdklab
2024-07-02 13:44 ` 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=20240701184525.1164582-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).