From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw113677 [PATCH v3] config/arm: add Phytium FT-2000+
Date: Tue, 5 Jul 2022 10:38:56 -0400 [thread overview]
Message-ID: <20220705143856.27938-1-robot@bytheb.org> (raw)
In-Reply-To: <20220705133057.3821347-1-thomas@monjalon.net>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/113677/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2616558583
next prev parent reply other threads:[~2022-07-05 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220705133057.3821347-1-thomas@monjalon.net>
2022-07-05 13:32 ` checkpatch
2022-07-05 14:38 ` 0-day Robot [this message]
2022-07-05 14:31 |SUCCESS| pw113677 [PATCH] [v3] " dpdklab
2022-07-05 15:13 dpdklab
2022-07-05 15:29 dpdklab
2022-07-05 15:44 dpdklab
2022-07-05 15:47 dpdklab
2022-07-05 15:51 dpdklab
2022-07-05 16:55 dpdklab
2022-07-05 16:59 dpdklab
2022-07-05 17:10 dpdklab
2022-07-05 19:05 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=20220705143856.27938-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).