From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw143184 [PATCH v2] doc: add new driver guidelines
Date: Wed, 14 Aug 2024 21:09:41 +0200 (CEST) [thread overview]
Message-ID: <20240814190941.82104123EF6@dpdk.org> (raw)
In-Reply-To: <20240814190901.14912-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143184
_coding style issues_
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#91:
Co-authored-by: Ferruh Yigit <ferruh.yigit@amd.com>
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#92:
Co-authored-by: Thomas Monjalon <thomas@monjalon.net>
total: 0 errors, 2 warnings, 209 lines checked
next prev parent reply other threads:[~2024-08-14 19:09 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240814190901.14912-1-stephen@networkplumber.org>
2024-08-14 18:42 ` |SUCCESS| " qemudev
2024-08-14 18:46 ` qemudev
2024-08-14 19:09 ` checkpatch [this message]
2024-08-14 20:02 ` 0-day Robot
2024-08-15 9:49 ` |SUCCESS| pw143184 [PATCH] [v2] " dpdklab
2024-08-15 9:52 ` dpdklab
2024-08-15 10:00 ` dpdklab
2024-08-15 10:01 ` dpdklab
2024-08-15 10:07 ` dpdklab
2024-08-15 10:08 ` dpdklab
2024-08-15 10:11 ` dpdklab
2024-08-15 10:12 ` |PENDING| " dpdklab
2024-08-15 10:12 ` |SUCCESS| " dpdklab
2024-08-15 10:12 ` dpdklab
2024-08-15 10:13 ` dpdklab
2024-08-15 10:17 ` |PENDING| " dpdklab
2024-08-15 10:18 ` |SUCCESS| " dpdklab
2024-08-15 10:18 ` |PENDING| " dpdklab
2024-08-15 10:19 ` |SUCCESS| " dpdklab
2024-08-15 10:20 ` |PENDING| " dpdklab
2024-08-15 10:20 ` |SUCCESS| " dpdklab
2024-08-15 10:22 ` |PENDING| " dpdklab
2024-08-15 10:26 ` dpdklab
2024-08-15 10:27 ` dpdklab
2024-08-15 10:28 ` dpdklab
2024-08-15 10:28 ` dpdklab
2024-08-15 10:28 ` dpdklab
2024-08-15 10:28 ` |SUCCESS| " dpdklab
2024-08-15 10:29 ` |PENDING| " dpdklab
2024-08-15 10:29 ` dpdklab
2024-08-15 10:30 ` dpdklab
2024-08-15 10:34 ` dpdklab
2024-08-15 10:34 ` dpdklab
2024-08-15 10:35 ` |SUCCESS| " dpdklab
2024-08-15 10:36 ` |PENDING| " dpdklab
2024-08-15 10:37 ` dpdklab
2024-08-15 10:40 ` dpdklab
2024-08-15 10:40 ` dpdklab
2024-08-15 10:40 ` dpdklab
2024-08-15 10:41 ` dpdklab
2024-08-15 10:42 ` dpdklab
2024-08-15 10:44 ` dpdklab
2024-08-15 10:45 ` dpdklab
2024-08-15 10:47 ` |SUCCESS| " dpdklab
2024-08-15 10:48 ` |PENDING| " dpdklab
2024-08-15 10:49 ` dpdklab
2024-08-15 10:51 ` dpdklab
2024-08-15 10:57 ` dpdklab
2024-08-15 10:57 ` |SUCCESS| " dpdklab
2024-08-15 10:57 ` |PENDING| " dpdklab
2024-08-15 10:59 ` dpdklab
2024-08-15 10:59 ` dpdklab
2024-08-15 11:01 ` dpdklab
2024-08-15 11:01 ` |SUCCESS| " dpdklab
2024-08-15 11:01 ` dpdklab
2024-08-15 11:02 ` dpdklab
2024-08-15 11:02 ` |PENDING| " dpdklab
2024-08-15 11:04 ` |SUCCESS| " dpdklab
2024-08-15 11:05 ` dpdklab
2024-08-15 11:19 ` dpdklab
2024-08-15 11:23 ` dpdklab
2024-08-15 11:28 ` |PENDING| " dpdklab
2024-08-15 11:30 ` dpdklab
2024-08-15 11:31 ` dpdklab
2024-08-15 11:31 ` dpdklab
2024-08-15 11:31 ` dpdklab
2024-08-15 11:33 ` dpdklab
2024-08-15 11:33 ` dpdklab
2024-08-15 11:33 ` dpdklab
2024-08-15 11:33 ` dpdklab
2024-08-15 11:34 ` dpdklab
2024-08-15 11:34 ` dpdklab
2024-08-15 11:35 ` dpdklab
2024-08-15 11:35 ` dpdklab
2024-08-15 11:35 ` dpdklab
2024-08-15 11:35 ` dpdklab
2024-08-15 11:36 ` dpdklab
2024-08-15 11:37 ` dpdklab
2024-08-15 11:37 ` dpdklab
2024-08-15 11:37 ` dpdklab
2024-08-15 11:38 ` dpdklab
2024-08-15 11:38 ` dpdklab
2024-08-15 11:38 ` dpdklab
2024-08-15 11:39 ` dpdklab
2024-08-15 11:40 ` dpdklab
2024-08-15 11:40 ` dpdklab
2024-08-15 11:41 ` dpdklab
2024-08-15 11:41 ` dpdklab
2024-08-15 11:43 ` |SUCCESS| " dpdklab
2024-08-15 11:45 ` |PENDING| " dpdklab
2024-08-15 12:23 ` dpdklab
2024-08-15 13:02 ` |SUCCESS| " dpdklab
2024-08-15 13:30 ` dpdklab
2024-08-15 13:40 ` dpdklab
2024-08-15 13:41 ` 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=20240814190941.82104123EF6@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).