From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Warrington, Jeffrey" <jwarrington@verisign.com>
Subject: |WARNING| pw134046 [PATCH v2] lpm: improve performance with copious IPv4 peering routes
Date: Fri, 10 Nov 2023 00:12:12 +0100 (CET) [thread overview]
Message-ID: <20231109231213.06C02120DB4@dpdk.org> (raw)
In-Reply-To: <0d975b44d6d443abaa00c02a1967c6b7@verisign.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/134046
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#85:
Co-authored-by: Julien Charbon <jcharbon@verisign.com>
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#88:
Co-authored-by: Nicolas Witkowski <nwitkowski@verisign.com>
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#90:
Co-authored-by: Rohit Gupta <rogupta@verisign.com>
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: "Warrington, Jeffrey" <jwarrington@verisign.com>' != 'Signed-off-by: Jeff Warrington <jwarrington@verisign.com>'
total: 0 errors, 4 warnings, 549 lines checked
next prev parent reply other threads:[~2023-11-09 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0d975b44d6d443abaa00c02a1967c6b7@verisign.com>
2023-11-09 22:51 ` |SUCCESS| " qemudev
2023-11-09 22:55 ` qemudev
2023-11-09 23:12 ` checkpatch [this message]
2023-11-09 23:59 ` 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=20231109231213.06C02120DB4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jwarrington@verisign.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).