From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ronak Doshi <ronak.doshi@broadcom.com>
Subject: |WARNING| pw139477 [PATCH] net/vmxnet3: fix a missing vmxnet3 register command
Date: Thu, 18 Apr 2024 08:06:41 +0200 (CEST) [thread overview]
Message-ID: <20240418060641.C472712083E@dpdk.org> (raw)
In-Reply-To: <20240418055658.24500-1-ronak.doshi@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139477
_coding style issues_
WARNING:TYPO_SPELLING: 'advertize' may be misspelled - perhaps 'advertise'?
#51:
Vmxnet3 uses capability registers to advertize the supported
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#76: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:129:
+ VMXNET3_CMD_RESERVED11,$
total: 0 errors, 2 warnings, 0 checks, 7 lines checked
next prev parent reply other threads:[~2024-04-18 6:16 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418055658.24500-1-ronak.doshi@broadcom.com>
2024-04-18 5:45 ` |SUCCESS| " qemudev
2024-04-18 5:49 ` qemudev
2024-04-18 6:06 ` checkpatch [this message]
2024-04-18 7:04 ` 0-day Robot
2024-04-18 7:14 ` |SUCCESS| pw139477 [PATCH] net/vmxnet3: fix a missing vmxnet3 regist dpdklab
2024-04-18 7:17 ` dpdklab
2024-04-18 7:20 ` dpdklab
2024-04-18 7:20 ` dpdklab
2024-04-18 7:20 ` dpdklab
2024-04-18 7:21 ` dpdklab
2024-04-18 7:22 ` dpdklab
2024-04-18 7:23 ` dpdklab
2024-04-18 7:24 ` dpdklab
2024-04-18 7:24 ` dpdklab
2024-04-18 7:24 ` dpdklab
2024-04-18 7:30 ` dpdklab
2024-04-18 7:31 ` dpdklab
2024-04-18 7:32 ` dpdklab
2024-04-18 7:34 ` dpdklab
2024-04-18 7:34 ` dpdklab
2024-04-18 7:42 ` dpdklab
2024-04-18 7:42 ` dpdklab
2024-04-18 7:55 ` dpdklab
2024-04-18 7:56 ` dpdklab
2024-04-18 7:57 ` dpdklab
2024-04-18 7:58 ` dpdklab
2024-04-18 7:59 ` dpdklab
2024-04-18 8:00 ` dpdklab
2024-04-18 8:01 ` dpdklab
2024-04-18 8:01 ` dpdklab
2024-04-18 8:02 ` dpdklab
2024-04-18 8:03 ` dpdklab
2024-04-18 8:03 ` dpdklab
2024-04-18 8:03 ` dpdklab
2024-04-18 8:04 ` dpdklab
2024-04-18 8:04 ` dpdklab
2024-04-18 8:04 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:06 ` dpdklab
2024-04-18 8:06 ` dpdklab
2024-04-18 8:06 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:08 ` dpdklab
2024-04-18 8:08 ` dpdklab
2024-04-18 8:08 ` dpdklab
2024-04-18 8:09 ` dpdklab
2024-04-18 8:09 ` dpdklab
2024-04-18 8:09 ` dpdklab
2024-04-18 8:10 ` dpdklab
2024-04-18 8:10 ` dpdklab
2024-04-18 8:11 ` dpdklab
2024-04-18 8:11 ` dpdklab
2024-04-18 8:11 ` dpdklab
2024-04-18 8:12 ` dpdklab
2024-04-18 8:13 ` dpdklab
2024-04-18 8:13 ` dpdklab
2024-04-18 8:14 ` dpdklab
2024-04-18 8:15 ` dpdklab
2024-04-18 8:15 ` dpdklab
2024-04-18 8:15 ` dpdklab
2024-04-18 8:16 ` dpdklab
2024-04-18 8:16 ` dpdklab
2024-04-18 8:17 ` dpdklab
2024-04-18 8:17 ` dpdklab
2024-04-18 8:17 ` dpdklab
2024-04-18 8:18 ` dpdklab
2024-04-18 8:19 ` dpdklab
2024-04-18 8:20 ` dpdklab
2024-04-18 8:21 ` dpdklab
2024-04-18 8:22 ` dpdklab
2024-04-18 8:22 ` dpdklab
2024-04-18 8:23 ` dpdklab
2024-04-18 8:30 ` dpdklab
2024-04-18 8:36 ` dpdklab
2024-04-18 8:48 ` dpdklab
2024-04-18 9:12 ` dpdklab
2024-04-18 9:58 ` dpdklab
2024-04-18 10:09 ` dpdklab
2024-04-18 10:10 ` dpdklab
2024-04-18 10:12 ` dpdklab
2024-04-18 10:38 ` dpdklab
2024-04-18 10:53 ` dpdklab
2024-04-18 10:53 ` dpdklab
2024-04-18 12:03 ` dpdklab
2024-04-18 12:33 ` 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=20240418060641.C472712083E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ronak.doshi@broadcom.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).