automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: |WARNING| pw158820 [PATCH v2] devtools: ignore new warnings on reported-by tag
Date: Fri, 14 Nov 2025 21:07:48 +0100 (CET)	[thread overview]
Message-ID: <20251114200748.44D661261F3@dpdk.org> (raw)
In-Reply-To: <20251114200640.1639056-1-dsosnowski@nvidia.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158820

_coding style issues_

Must be a reply to the first patch (--in-reply-to).


WARNING:BAD_SIGN_OFF: Do not use whitespace before Reported-by:
#124: 
      Reported-by: should be immediately followed by Closes:

ERROR:BAD_SIGN_OFF: Unrecognized email address: 'should be immediately followed by Closes:'
#124: 
      Reported-by: should be immediately followed by Closes:

WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#134: 
[1]: https://github.com/torvalds/linux/commit/d7f1d71e5ef630ab9e15b5821d297a9e1a5fa1da

total: 1 errors, 2 warnings, 8 lines checked

  parent reply	other threads:[~2025-11-14 20:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251114200640.1639056-1-dsosnowski@nvidia.com>
2025-11-14 19:33 ` |SUCCESS| " qemudev
2025-11-14 19:38 ` qemudev
2025-11-14 20:07 ` checkpatch [this message]
2025-11-14 20:57 ` |SUCCESS| pw158820 [PATCH] [v2] devtools: ignore new warnings on rep dpdklab
2025-11-14 21:06 ` dpdklab
2025-11-14 21:07 ` dpdklab
2025-11-14 21:13 ` dpdklab
2025-11-14 21:19 ` dpdklab
2025-11-14 21:29 ` |SUCCESS| pw158820 [PATCH v2] devtools: ignore new warnings on reported-by tag 0-day Robot
2025-11-14 21:29 ` 0-day Robot
2025-11-14 21:30 ` |SUCCESS| pw158820 [PATCH] [v2] devtools: ignore new warnings on rep dpdklab
2025-11-14 21:35 ` dpdklab
2025-11-14 21:35 ` dpdklab
2025-11-14 21:37 ` |PENDING| " dpdklab
2025-11-14 22:43 ` |SUCCESS| " dpdklab
2025-11-14 22:53 ` dpdklab
2025-11-14 23:02 ` dpdklab
2025-11-14 23:04 ` dpdklab
2025-11-14 23:59 ` dpdklab
2025-11-15  4:21 ` dpdklab
2025-11-15  8:37 ` dpdklab
2025-11-15 11:05 ` dpdklab
2025-11-15 11:10 ` dpdklab
2025-11-15 12:48 ` dpdklab
2025-11-15 13:05 ` dpdklab
2025-11-15 13:48 ` dpdklab
2025-11-15 13:50 ` dpdklab
2025-11-15 14:47 ` dpdklab
2025-11-15 14:47 ` dpdklab
2025-11-15 14:48 ` dpdklab
2025-11-15 14:48 ` 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=20251114200748.44D661261F3@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=dsosnowski@nvidia.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).