From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Subject: |WARNING| pw106345 [PATCH v2] net/tap: fix to populate fds in secondary process
Date: Mon, 24 Jan 2022 13:13:50 +0100 (CET) [thread overview]
Message-ID: <20220124121350.CA816120767@dpdk.org> (raw)
In-Reply-To: <20220124121251.64762-1-kumaraparamesh92@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106345
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#381: FILE: lib/ethdev/ethdev_driver.h:1633:
+/**
+* Get rte_eth_dev from device name. The device name should be specified
total: 0 errors, 1 warnings, 307 lines checked
next parent reply other threads:[~2022-01-24 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220124121251.64762-1-kumaraparamesh92@gmail.com>
2022-01-24 12:13 ` checkpatch [this message]
2022-01-24 13:39 ` |SUCCESS| " 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=20220124121350.CA816120767@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kumaraparamesh92@gmail.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).