From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw150146 [PATCH] .mailmap: resort entries
Date: Thu, 16 Jan 2025 18:11:20 +0100 (CET) [thread overview]
Message-ID: <20250116171120.CBE99126FE3@dpdk.org> (raw)
In-Reply-To: <20250116171010.75942-1-stephen@networkplumber.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150146
_coding style issues_
WARNING:TYPO_SPELLING: 'Amin' may be misspelled - perhaps 'Main'?
#153: FILE: .mailmap:85:
+Amin Tootoonchian <amint@icsi.berkeley.edu>
WARNING:TYPO_SPELLING: 'ois' may be misspelled - perhaps 'is'?
#371: FILE: .mailmap:448:
+François-Frédéric Ozog <ff@ozog.com>
WARNING:TYPO_SPELLING: 'Wan' may be misspelled - perhaps 'Want'?
#602: FILE: .mailmap:759:
+Junjie Wan <wanjunjie@bytedance.com>
WARNING:TYPO_SPELLING: 'Tim' may be misspelled - perhaps 'Time'?
#1065: FILE: .mailmap:1535:
+Tim Martin <timothym@nvidia.com>
WARNING:TYPO_SPELLING: 'Tim' may be misspelled - perhaps 'Time'?
#1066: FILE: .mailmap:1536:
+Tim Shearer <tim.shearer@overturenetworks.com>
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#1066: FILE: .mailmap:1536:
+Tim Shearer <tim.shearer@overturenetworks.com>
total: 0 errors, 6 warnings, 1148 lines checked
next prev parent reply other threads:[~2025-01-16 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250116171010.75942-1-stephen@networkplumber.org>
2025-01-16 16:39 ` |SUCCESS| " qemudev
2025-01-16 16:43 ` qemudev
2025-01-16 17:11 ` checkpatch [this message]
2025-01-16 18:07 ` 0-day Robot
2025-01-16 18:14 ` dpdklab
2025-01-16 18:14 ` dpdklab
2025-01-16 18:19 ` |PENDING| " dpdklab
2025-01-16 18:23 ` |SUCCESS| " dpdklab
2025-01-16 18:24 ` dpdklab
2025-01-16 18:25 ` |PENDING| " dpdklab
2025-01-16 18:26 ` |SUCCESS| " dpdklab
2025-01-16 18:29 ` |PENDING| " dpdklab
2025-01-16 18:33 ` |SUCCESS| " dpdklab
2025-01-16 18:36 ` |PENDING| " dpdklab
2025-01-16 18:41 ` dpdklab
2025-01-16 18:54 ` |SUCCESS| " dpdklab
2025-01-16 19:01 ` dpdklab
2025-01-16 19:06 ` dpdklab
2025-01-16 19:07 ` dpdklab
2025-01-16 19:07 ` dpdklab
2025-01-16 19:11 ` dpdklab
2025-01-16 19:27 ` dpdklab
2025-01-16 19:53 ` |WARNING| " dpdklab
2025-01-16 20:38 ` |SUCCESS| " 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=20250116171120.CBE99126FE3@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).