From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Marat Khalili <marat.khalili@huawei.com>
Subject: |WARNING| pw159330 [PATCH v2 5/5] bpf: fix BPF validation w/ conditional jump first
Date: Tue, 16 Dec 2025 19:21:17 +0100 (CET) [thread overview]
Message-ID: <20251216182117.92FCA1253F0@dpdk.org> (raw)
In-Reply-To: <20251216182036.77869-6-marat.khalili@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159330
_coding style issues_
WARNING:TYPO_SPELLING: 'demostrating' may be misspelled - perhaps 'demonstrating'?
#71:
Add two tests demostrating the problem:
^^^^^^^^^^^^
WARNING:TYPO_SPELLING: 'succeeed' may be misspelled - perhaps 'succeed'?
#73:
conditional jump over the invalid operation, should not succeeed;
^^^^^^^^
WARNING:TYPO_SPELLING: 'demostrate' may be misspelled - perhaps 'demonstrate'?
#75:
instruction at the start to demostrate that it is indeed invalid
^^^^^^^^^^
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: 6e12ec4c4d6d ("bpf: add more checks")'
#78:
Fixes: 6e12ec4c4d ("bpf: add more checks")
total: 0 errors, 4 warnings, 143 lines checked
next prev parent reply other threads:[~2025-12-16 18:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251216182036.77869-6-marat.khalili@huawei.com>
2025-12-16 18:01 ` |SUCCESS| pw159326-159330 " qemudev
2025-12-16 18:06 ` qemudev
2025-12-16 18:21 ` checkpatch [this message]
2025-12-16 19:32 ` |SUCCESS| pw159330 " 0-day Robot
2025-12-16 19:33 ` 0-day Robot
2025-12-16 20:04 ` |PENDING| pw159326-159330 [PATCH] [v2,5/5] bpf: fix BPF validation w dpdklab
2025-12-16 20:04 ` dpdklab
2025-12-16 20:13 ` dpdklab
2025-12-16 20:24 ` |SUCCESS| " dpdklab
2025-12-16 20:25 ` |PENDING| " dpdklab
2025-12-16 20:26 ` |SUCCESS| " dpdklab
2025-12-16 20:35 ` dpdklab
2025-12-16 20:42 ` dpdklab
2025-12-16 20:53 ` dpdklab
2025-12-16 21:00 ` dpdklab
2025-12-16 21:04 ` dpdklab
2025-12-16 21:50 ` dpdklab
2025-12-16 23:25 ` 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=20251216182117.92FCA1253F0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=marat.khalili@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).