From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137370 [PATCH] common/cnxk: fix link cfg for sdp
Date: Tue, 27 Feb 2024 19:56:23 +0100 (CET) [thread overview]
Message-ID: <20240227185623.DFAB6122320@dpdk.org> (raw)
In-Reply-To: <20240227185519.7711-1-hkalra@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137370
_coding style OK_
next prev parent reply other threads:[~2024-02-27 18:56 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227185519.7711-1-hkalra@marvell.com>
2024-02-27 18:31 ` qemudev
2024-02-27 18:36 ` qemudev
2024-02-27 18:56 ` checkpatch [this message]
2024-02-27 19:45 ` 0-day Robot
2024-02-27 20:53 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:17 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:19 ` dpdklab
2024-02-27 21:19 ` dpdklab
2024-02-27 21:33 ` dpdklab
2024-02-27 21:33 ` dpdklab
2024-02-27 21:39 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:02 ` dpdklab
2024-02-28 1:03 ` dpdklab
2024-02-28 1:03 ` dpdklab
2024-02-28 1:08 ` dpdklab
2024-02-28 1:08 ` dpdklab
2024-02-28 1:09 ` dpdklab
2024-02-28 1:09 ` dpdklab
2024-02-28 1:10 ` dpdklab
2024-02-28 1:11 ` dpdklab
2024-02-28 1:11 ` dpdklab
2024-02-28 1:12 ` dpdklab
2024-02-28 1:12 ` dpdklab
2024-02-28 1:12 ` dpdklab
2024-02-28 1:12 ` dpdklab
2024-02-28 1:12 ` dpdklab
2024-02-28 1:13 ` dpdklab
2024-02-28 1:15 ` dpdklab
2024-02-28 1:15 ` dpdklab
2024-02-28 1:18 ` dpdklab
2024-02-28 1:20 ` dpdklab
2024-02-28 1:20 ` dpdklab
2024-02-28 1:21 ` dpdklab
2024-02-28 1:21 ` dpdklab
2024-02-28 1:29 ` dpdklab
2024-02-28 1:30 ` dpdklab
2024-02-28 1:30 ` dpdklab
2024-02-28 1:36 ` dpdklab
2024-02-28 1:38 ` dpdklab
2024-02-28 1:40 ` dpdklab
2024-02-28 1:40 ` dpdklab
2024-02-28 2:11 ` dpdklab
2024-02-28 2:12 ` dpdklab
2024-02-28 2:13 ` dpdklab
2024-02-28 2:16 ` dpdklab
2024-02-28 2:23 ` dpdklab
2024-02-28 2:25 ` dpdklab
2024-02-28 2:39 ` dpdklab
2024-02-28 3:00 ` dpdklab
2024-02-28 4:07 ` dpdklab
2024-02-28 4:08 ` dpdklab
2024-02-28 9:19 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:26 ` dpdklab
2024-02-28 20:13 ` dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 15:28 ` dpdklab
2024-02-29 15:36 ` dpdklab
2024-02-29 15:40 ` dpdklab
2024-02-29 15:43 ` 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=20240227185623.DFAB6122320@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).