From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw135286 [PATCH] mempool/dpaa2: use driver logtype not PMD
Date: Mon, 18 Dec 2023 13:26:54 -0500 [thread overview]
Message-ID: <20231218182654.2641002-1-robot@bytheb.org> (raw)
In-Reply-To: <20231218171909.248658-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/135286/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7251822253
next prev parent reply other threads:[~2023-12-18 18:26 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231218171909.248658-1-stephen@networkplumber.org>
2023-12-18 16:59 ` qemudev
2023-12-18 17:04 ` qemudev
2023-12-18 17:19 ` checkpatch
2023-12-18 18:26 ` 0-day Robot [this message]
2023-12-18 19:05 dpdklab
2023-12-18 19:10 dpdklab
2023-12-18 19:15 dpdklab
2023-12-18 19:15 dpdklab
2023-12-18 19:16 dpdklab
2023-12-18 19:16 dpdklab
2023-12-18 19:17 dpdklab
2023-12-18 19:18 dpdklab
2023-12-18 19:24 dpdklab
2023-12-18 19:26 dpdklab
2023-12-18 19:27 dpdklab
2023-12-18 19:28 dpdklab
2023-12-18 19:29 dpdklab
2023-12-18 19:30 dpdklab
2023-12-18 19:31 dpdklab
2023-12-18 19:32 dpdklab
2023-12-18 19:32 dpdklab
2023-12-18 19:33 dpdklab
2023-12-18 19:33 dpdklab
2023-12-18 19:50 dpdklab
2023-12-18 19:52 dpdklab
2023-12-18 19:55 dpdklab
2023-12-18 20:09 dpdklab
2023-12-18 20:11 dpdklab
2023-12-18 20:14 dpdklab
2023-12-18 20:15 dpdklab
2023-12-18 20:16 dpdklab
2023-12-18 20:19 dpdklab
2023-12-18 20:21 dpdklab
2023-12-18 20:24 dpdklab
2023-12-18 20:24 dpdklab
2023-12-18 20:25 dpdklab
2023-12-18 20:26 dpdklab
2023-12-18 20:27 dpdklab
2023-12-18 20:30 dpdklab
2023-12-18 20:30 dpdklab
2023-12-18 20:33 dpdklab
2023-12-18 20:34 dpdklab
2023-12-18 20:35 dpdklab
2023-12-18 20:36 dpdklab
2023-12-18 20:37 dpdklab
2023-12-18 20:37 dpdklab
2023-12-18 20:40 dpdklab
2023-12-18 20:41 dpdklab
2023-12-18 20:44 dpdklab
2023-12-18 20:46 dpdklab
2023-12-18 20:48 dpdklab
2023-12-18 20:53 dpdklab
2023-12-18 20:56 dpdklab
2023-12-18 20:56 dpdklab
2023-12-18 20:58 dpdklab
2023-12-18 20:58 dpdklab
2023-12-18 20:59 dpdklab
2023-12-18 21:05 dpdklab
2023-12-18 21:07 dpdklab
2023-12-18 21:08 dpdklab
2023-12-18 21:08 dpdklab
2023-12-18 21:11 dpdklab
2023-12-18 21:12 dpdklab
2023-12-18 21:18 dpdklab
2023-12-18 21:20 dpdklab
2023-12-18 21:24 dpdklab
2023-12-18 21:29 dpdklab
2023-12-18 21:31 dpdklab
2023-12-18 21:44 dpdklab
2023-12-18 21:48 dpdklab
2023-12-18 22:04 dpdklab
2023-12-18 22:58 dpdklab
2023-12-18 23:12 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=20231218182654.2641002-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).