From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stefan Laesser <stefan.laesser@omicronenergy.com>
Subject: |WARNING| pw150145 [PATCH] net/af_packet: provide packet drop stats
Date: Thu, 16 Jan 2025 17:17:40 +0100 (CET) [thread overview]
Message-ID: <20250116161740.0BEB6126FE3@dpdk.org> (raw)
In-Reply-To: <20250116161703.917279-1-stefan.laesser@omicronenergy.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150145
_coding style issues_
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#121:
Next, I have added a counter for the case when mbuf couldn't be
total: 0 errors, 1 warnings, 0 checks, 73 lines checked
next prev parent reply other threads:[~2025-01-16 16:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250116161703.917279-1-stefan.laesser@omicronenergy.com>
2025-01-16 15:47 ` |SUCCESS| " qemudev
2025-01-16 15:51 ` qemudev
2025-01-16 16:17 ` checkpatch [this message]
2025-01-16 16:51 ` |PENDING| " dpdklab
2025-01-16 16:55 ` dpdklab
2025-01-16 16:57 ` dpdklab
2025-01-16 16:58 ` |SUCCESS| " dpdklab
2025-01-16 17:04 ` dpdklab
2025-01-16 17:05 ` 0-day Robot
2025-01-16 17:05 ` |PENDING| " dpdklab
2025-01-16 17:07 ` dpdklab
2025-01-16 17:10 ` |SUCCESS| " dpdklab
2025-01-16 17:15 ` dpdklab
2025-01-16 17:17 ` dpdklab
2025-01-16 17:19 ` dpdklab
2025-01-16 17:20 ` dpdklab
2025-01-16 17:27 ` dpdklab
2025-01-16 17:27 ` dpdklab
2025-01-16 17:28 ` dpdklab
2025-01-16 17:32 ` dpdklab
2025-01-16 17:43 ` dpdklab
2025-01-16 17:54 ` dpdklab
2025-01-16 18:05 ` |WARNING| " dpdklab
2025-01-16 18:05 ` |SUCCESS| " dpdklab
2025-01-16 18:56 ` 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=20250116161740.0BEB6126FE3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stefan.laesser@omicronenergy.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).