From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw136632 [PATCH] maintainers: add myself to usertools
Date: Tue, 13 Feb 2024 06:04:23 -0500 [thread overview]
Message-ID: <20240213110423.3360309-1-robot@bytheb.org> (raw)
In-Reply-To: <20240213095851.60315-2-rjarry@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/136632/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7885064807
next prev parent reply other threads:[~2024-02-13 11:04 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240213095851.60315-2-rjarry@redhat.com>
2024-02-13 9:37 ` qemudev
2024-02-13 9:41 ` qemudev
2024-02-13 9:59 ` checkpatch
2024-02-13 11:04 ` 0-day Robot [this message]
2024-02-13 10:32 dpdklab
2024-02-13 10:32 dpdklab
2024-02-13 10:32 dpdklab
2024-02-13 10:33 dpdklab
2024-02-13 10:33 dpdklab
2024-02-13 10:41 dpdklab
2024-02-13 10:42 dpdklab
2024-02-13 10:42 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:44 dpdklab
2024-02-13 10:44 dpdklab
2024-02-13 10:44 dpdklab
2024-02-13 10:45 dpdklab
2024-02-13 10:45 dpdklab
2024-02-13 10:46 dpdklab
2024-02-13 10:46 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:49 dpdklab
2024-02-13 10:49 dpdklab
2024-02-13 10:49 dpdklab
2024-02-13 10:50 dpdklab
2024-02-13 10:50 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:52 dpdklab
2024-02-13 10:52 dpdklab
2024-02-13 10:52 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:54 dpdklab
2024-02-13 10:54 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 11:03 dpdklab
2024-02-13 11:06 dpdklab
2024-02-13 11:19 dpdklab
2024-02-13 11:22 dpdklab
2024-02-13 11:22 dpdklab
2024-02-13 11:23 dpdklab
2024-02-13 11:36 dpdklab
2024-02-13 11:36 dpdklab
2024-02-13 11:37 dpdklab
2024-02-13 12: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=20240213110423.3360309-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).