From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Thierry Herbelot <thierry.herbelot@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw93385 [PATCH] vhost/vhost_crypto: do not use possibly NULL Pointers
Date: Mon, 24 May 2021 10:58:55 +0200 (CEST) [thread overview]
Message-ID: <20210524085855.EC35C122E1E@dpdk.org> (raw)
In-Reply-To: <20210524085812.15916-1-thierry.herbelot@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93385
_coding style issues_
WARNING:SUSPECT_COMMA_SEMICOLON: Possible comma where semicolon could be used
#78: FILE: lib/vhost/vhost_crypto.c:1348:
+ used_idx = vc_req->desc_idx, desc_idx;
total: 0 errors, 1 warnings, 17 lines checked
next parent reply other threads:[~2021-05-24 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210524085812.15916-1-thierry.herbelot@6wind.com>
2021-05-24 8:58 ` checkpatch [this message]
2021-05-24 10:58 ` [dpdk-test-report] |FAILURE| pw93385 [dpdk-dev] " 0-day Robot
2021-05-24 14:14 [dpdk-test-report] |WARNING| pw93385 " 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=20210524085855.EC35C122E1E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thierry.herbelot@6wind.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).