From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw94680 [PATCH] net/mlx5: fix multi-segment inline for the first segment
Date: Tue, 22 Jun 2021 18:42:39 +0200 (CEST) [thread overview]
Message-ID: <20210622164239.2CAEE122E3A@dpdk.org> (raw)
In-Reply-To: <20210622164049.9191-1-viacheslavo@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94680
_coding style issues_
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#169: FILE: drivers/net/mlx5/mlx5_tx.h:2064:
+ return mlx5_tx_packet_multi_send(txq, loc, olx);
+ } else {
total: 0 errors, 1 warnings, 0 checks, 53 lines checked
next parent reply other threads:[~2021-06-22 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210622164049.9191-1-viacheslavo@nvidia.com>
2021-06-22 16:42 ` checkpatch [this message]
2021-06-22 18:01 ` [dpdk-test-report] |SUCCESS| pw94680 [dpdk-dev] " 0-day Robot
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=20210622164239.2CAEE122E3A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=viacheslavo@nvidia.com \
/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).