From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mohand Alrasheed <mrasheed@wirefilter.com>
Subject: |WARNING| pw159602 [PATCH] net/mlx5: fix offset handling in mlx5_aso_cnt_sq_enqueue_burst
Date: Tue, 6 Jan 2026 10:50:35 +0100 (CET) [thread overview]
Message-ID: <20260106095035.BE45D124270@dpdk.org> (raw)
In-Reply-To: <205110942.16694617.1767623073046.JavaMail.zimbra@wirefilter.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159602
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#76:
Reproducible example: https://github.com/Hawzen/rte-flow-async-profiling/blob/5e654e3a8a0414a5fa8ed43274195f180760f0b5/examples/flow_filtering/reproduce.md
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: 4d368e1da3a4 ("net/mlx5: support flow counter action for HWS")'
#78:
Fixes: 4d368e1da3a453cbcac620e8844c0300b2f45cfa
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 2 warnings, 0 checks, 7 lines checked
next parent reply other threads:[~2026-01-06 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <205110942.16694617.1767623073046.JavaMail.zimbra@wirefilter.com>
2026-01-06 9:50 ` checkpatch [this message]
2026-01-06 10:45 ` |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=20260106095035.BE45D124270@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mrasheed@wirefilter.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).