From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jochen Behrens <jochen.behrens@broadcom.com>
Subject: |WARNING| pw139381 [PATCH] mailmap: clean up vmware entries
Date: Tue, 16 Apr 2024 01:41:02 +0200 (CEST) [thread overview]
Message-ID: <20240415234102.2953412083E@dpdk.org> (raw)
In-Reply-To: <20240415233935.1913135-1-jochen.behrens@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139381
_coding style issues_
WARNING:TYPO_SPELLING: 'Ang' may be misspelled - perhaps 'And'?
#108: FILE: .mailmap:187:
+Boon Ang <boon.ang@broadcom.com>
WARNING:TYPO_SPELLING: 'ang' may be misspelled - perhaps 'and'?
#108: FILE: .mailmap:187:
+Boon Ang <boon.ang@broadcom.com>
total: 0 errors, 2 warnings, 124 lines checked
next prev parent reply other threads:[~2024-04-15 23:41 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240415233935.1913135-1-jochen.behrens@broadcom.com>
2024-04-15 23:17 ` |SUCCESS| " qemudev
2024-04-15 23:22 ` qemudev
2024-04-15 23:41 ` checkpatch [this message]
2024-04-16 0:24 ` 0-day Robot
2024-04-16 10:00 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:03 ` dpdklab
2024-04-16 10:31 ` dpdklab
2024-04-16 10:41 ` dpdklab
2024-04-16 10:42 ` dpdklab
2024-04-16 10:43 ` dpdklab
2024-04-16 10:44 ` dpdklab
2024-04-16 10:45 ` dpdklab
2024-04-16 10:46 ` dpdklab
2024-04-16 10:49 ` dpdklab
2024-04-16 10:51 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:58 ` dpdklab
2024-04-16 10:59 ` dpdklab
2024-04-16 10:59 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:02 ` dpdklab
2024-04-16 11:05 ` dpdklab
2024-04-16 11:05 ` dpdklab
2024-04-16 11:09 ` dpdklab
2024-04-16 11:09 ` dpdklab
2024-04-16 11:13 ` dpdklab
2024-04-16 11:13 ` dpdklab
2024-04-16 11:14 ` dpdklab
2024-04-16 11:15 ` dpdklab
2024-04-16 11:16 ` dpdklab
2024-04-16 11:17 ` dpdklab
2024-04-16 11:19 ` dpdklab
2024-04-16 11:22 ` dpdklab
2024-04-16 11:22 ` dpdklab
2024-04-16 11:26 ` dpdklab
2024-04-16 11:26 ` dpdklab
2024-04-16 11:26 ` dpdklab
2024-04-16 11:26 ` dpdklab
2024-04-16 11:27 ` dpdklab
2024-04-16 11:27 ` dpdklab
2024-04-16 11:28 ` dpdklab
2024-04-16 11:30 ` dpdklab
2024-04-16 11:30 ` dpdklab
2024-04-16 11:31 ` dpdklab
2024-04-16 11:33 ` dpdklab
2024-04-16 11:33 ` dpdklab
2024-04-16 11:38 ` dpdklab
2024-04-16 11:39 ` dpdklab
2024-04-16 11:39 ` dpdklab
2024-04-16 11:42 ` dpdklab
2024-04-16 11:42 ` dpdklab
2024-04-16 11:45 ` dpdklab
2024-04-16 11:45 ` dpdklab
2024-04-16 11:46 ` dpdklab
2024-04-16 11:50 ` dpdklab
2024-04-16 11:51 ` dpdklab
2024-04-16 11:53 ` dpdklab
2024-04-16 11:53 ` dpdklab
2024-04-16 11:57 ` dpdklab
2024-04-16 11:57 ` dpdklab
2024-04-16 11:59 ` dpdklab
2024-04-16 12:01 ` dpdklab
2024-04-16 12:02 ` dpdklab
2024-04-16 12:03 ` dpdklab
2024-04-16 12:05 ` dpdklab
2024-04-16 12:06 ` dpdklab
2024-04-16 12:12 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:16 ` dpdklab
2024-04-16 12:19 ` dpdklab
2024-04-16 12:20 ` dpdklab
2024-04-16 12:21 ` dpdklab
2024-04-16 12:23 ` dpdklab
2024-04-16 12:23 ` dpdklab
2024-04-16 12:26 ` dpdklab
2024-04-16 12:27 ` dpdklab
2024-04-16 12:30 ` dpdklab
2024-04-16 12:38 ` dpdklab
2024-04-16 13:24 ` dpdklab
2024-04-16 13:45 ` dpdklab
2024-04-16 15:00 ` 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=20240415234102.2953412083E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jochen.behrens@broadcom.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).