From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw122351 [PATCH 2/2] net/vhost: support private dump
Date: Thu, 19 Jan 2023 13:38:40 +0100 (CET) [thread overview]
Message-ID: <20230119123840.75282123D76@dpdk.org> (raw)
In-Reply-To: <20230119123056.14338-3-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/122351
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#76: FILE: drivers/net/vhost/rte_eth_vhost.c:1493:
+ fprintf(f, "flags: 0x%" PRIx64 "
", internal->flags);
total: 0 errors, 0 warnings, 1 checks, 33 lines checked
Warning in drivers/net/vhost/rte_eth_vhost.c:
Using rte_atomicNN_xxx
next prev parent reply other threads:[~2023-01-19 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230119123056.14338-3-fengchengwen@huawei.com>
2023-01-19 12:30 ` |SUCCESS| pw122352-122351 " qemudev
2023-01-19 12:34 ` qemudev
2023-01-19 12:38 ` checkpatch [this message]
2023-01-19 14:19 ` |SUCCESS| pw122351 " 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=20230119123840.75282123D76@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=fengchengwen@huawei.com \
--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).