automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141293 [PATCH v2] net/mlx5: fix incorrect rx/tx descriptor limitations in rte_eth_dev_info
Date: Wed, 19 Jun 2024 01:00:03 +0200 (CEST)	[thread overview]
Message-ID: <20240618230003.C34A412231F@dpdk.org> (raw)
In-Reply-To: <20240618225642.1036624-2-igootorov@gmail.com>

Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141293

_coding style OK_



  parent reply	other threads:[~2024-06-18 23:00 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240618225642.1036624-2-igootorov@gmail.com>
2024-06-18 22:31 ` qemudev
2024-06-18 22:35 ` qemudev
2024-06-18 23:00 ` checkpatch [this message]
2024-06-19  0:04 ` 0-day Robot
2024-06-19  3:38 ` |SUCCESS| pw141293 [PATCH] [v2] net/mlx5: fix incorrect rx/tx descri dpdklab
2024-06-19  3:42 ` dpdklab
2024-06-19  3:43 ` dpdklab
2024-06-19  3:45 ` dpdklab
2024-06-19  3:45 ` dpdklab
2024-06-19  3:49 ` dpdklab
2024-06-19  3:49 ` dpdklab
2024-06-19  3:52 ` dpdklab
2024-06-19  3:53 ` dpdklab
2024-06-19  3:53 ` dpdklab
2024-06-19  3:54 ` dpdklab
2024-06-19  3:56 ` dpdklab
2024-06-19  3:59 ` dpdklab
2024-06-19  4:22 ` dpdklab
2024-06-19  4:29 ` dpdklab
2024-06-19  4:30 ` dpdklab
2024-06-19  5:37 ` dpdklab
2024-06-19  5:42 ` dpdklab
2024-06-19  5:44 ` dpdklab
2024-06-19  5:47 ` dpdklab
2024-06-19  5:48 ` dpdklab
2024-06-19  5:57 ` dpdklab
2024-06-19  6:13 ` dpdklab
2024-06-19  7:57 ` dpdklab
2024-06-19  7:57 ` dpdklab
2024-06-19  7:58 ` dpdklab
2024-06-19  7:58 ` dpdklab
2024-06-19  8:03 ` dpdklab
2024-06-19  8:04 ` dpdklab
2024-06-19  8:05 ` dpdklab
2024-06-19  8:05 ` dpdklab
2024-06-19  8:07 ` dpdklab
2024-06-19  8:20 ` dpdklab
2024-06-19  8:21 ` dpdklab
2024-06-19  8:25 ` dpdklab
2024-06-19  8:31 ` dpdklab
2024-06-19  8:32 ` dpdklab
2024-06-19  8:57 ` dpdklab
2024-06-19  9:17 ` dpdklab
2024-06-19  9:17 ` dpdklab
2024-06-19  9:18 ` dpdklab
2024-06-19  9:39 ` dpdklab
2024-06-19  9:39 ` dpdklab
2024-06-19  9:43 ` dpdklab
2024-06-19  9:43 ` dpdklab
2024-06-19  9:46 ` dpdklab
2024-06-19  9:48 ` dpdklab
2024-06-19  9:49 ` dpdklab
2024-06-19 10:12 ` dpdklab
2024-06-19 10:14 ` dpdklab
2024-06-19 10:16 ` dpdklab
2024-06-19 10:16 ` dpdklab
2024-06-19 10:30 ` dpdklab
2024-06-19 10:31 ` dpdklab
2024-06-19 11:05 ` dpdklab
2024-06-19 11:10 ` dpdklab
2024-06-19 11:15 ` dpdklab
2024-06-19 11:18 ` dpdklab
2024-06-19 11:25 ` dpdklab
2024-06-19 11:34 ` dpdklab
2024-06-19 11:40 ` dpdklab
2024-06-19 11:40 ` dpdklab
2024-06-19 11:41 ` dpdklab
2024-06-19 11:41 ` dpdklab
2024-06-19 11:42 ` dpdklab
2024-06-19 11:42 ` dpdklab
2024-06-19 11:43 ` dpdklab
2024-06-19 11:43 ` dpdklab
2024-06-19 11:44 ` dpdklab
2024-06-19 11:45 ` dpdklab
2024-06-19 11:46 ` dpdklab
2024-06-19 11:50 ` dpdklab
2024-06-19 11:51 ` dpdklab
2024-06-19 11:52 ` dpdklab
2024-06-19 11:56 ` dpdklab
2024-06-19 11:59 ` dpdklab
2024-06-19 11:59 ` dpdklab
2024-06-19 12:07 ` dpdklab
2024-06-19 12:10 ` dpdklab
2024-06-19 12:11 ` dpdklab
2024-06-19 12:20 ` dpdklab
2024-06-19 12:21 ` dpdklab
2024-06-19 12:24 ` dpdklab
2024-06-19 12:24 ` dpdklab
2024-06-19 12:25 ` dpdklab
2024-06-19 12:28 ` dpdklab
2024-06-19 12:30 ` dpdklab
2024-06-19 12:32 ` dpdklab
2024-06-19 12:36 ` dpdklab
2024-06-19 12:40 ` dpdklab
2024-06-19 12:48 ` dpdklab
2024-06-19 12:50 ` dpdklab
2024-06-19 12:54 ` dpdklab
2024-06-19 12:55 ` dpdklab
2024-06-19 12:56 ` dpdklab
2024-06-19 12:56 ` dpdklab
2024-06-19 13:03 ` dpdklab
2024-06-19 13:05 ` dpdklab
2024-06-19 13:29 ` dpdklab
2024-06-19 13:30 ` dpdklab
2024-06-19 13:35 ` dpdklab
2024-06-19 13:35 ` dpdklab
2024-06-19 13:39 ` dpdklab
2024-06-19 13:40 ` dpdklab
2024-06-19 14:02 ` dpdklab
2024-06-19 19:31 ` dpdklab
2024-06-19 19:46 ` dpdklab
2024-06-21 13:10 ` 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=20240618230003.C34A412231F@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).