From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw108429 [PATCH v2] common/mlx5: fix missing default devargs initialization
Date: Tue, 1 Mar 2022 12:11:23 +0100 (CET) [thread overview]
Message-ID: <20220301111123.786E71234A0@dpdk.org> (raw)
In-Reply-To: <20220301110935.3958252-1-michaelba@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/108429
_coding style OK_
next parent reply other threads:[~2022-03-01 11:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220301110935.3958252-1-michaelba@nvidia.com>
2022-03-01 11:11 ` checkpatch [this message]
2022-03-01 12:59 ` 0-day Robot
2022-03-01 23:41 |SUCCESS| pw108429 [PATCH] [v2] " dpdklab
2022-03-01 23:46 dpdklab
2022-03-02 0:12 dpdklab
2022-03-02 0:31 dpdklab
2022-03-02 0:45 dpdklab
2022-03-02 0:48 dpdklab
2022-03-02 1:00 dpdklab
2022-03-02 2:29 dpdklab
2022-03-02 2:44 dpdklab
2022-03-02 5:31 dpdklab
2022-03-02 6:13 dpdklab
2022-03-02 6:32 dpdklab
2022-03-02 19:05 dpdklab
2022-03-03 0:50 dpdklab
2022-03-03 1:28 dpdklab
2022-03-03 11:23 dpdklab
2022-03-04 13:48 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=20220301111123.786E71234A0@dpdk.org \
--to=checkpatch@dpdk.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).