From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138133 [PATCH v2] add a ignore list for get_maintainer
Date: Fri, 8 Mar 2024 19:13:27 +0100 (CET) [thread overview]
Message-ID: <20240308181327.38EC71223EF@dpdk.org> (raw)
In-Reply-To: <20240308181310.70014-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138133
_coding style issues_
WARNING:TYPO_SPELLING: 'Gage' may be misspelled - perhaps 'Gauge'?
#105: FILE: .get_maintainer.ignore:4:
+Gage Eads <gage.eads@intel.com>
WARNING:TYPO_SPELLING: 'gage' may be misspelled - perhaps 'gauge'?
#105: FILE: .get_maintainer.ignore:4:
+Gage Eads <gage.eads@intel.com>
total: 0 errors, 2 warnings, 11 lines checked
next prev parent reply other threads:[~2024-03-08 18:13 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308181310.70014-1-stephen@networkplumber.org>
2024-03-08 17:53 ` |SUCCESS| " qemudev
2024-03-08 17:58 ` qemudev
2024-03-08 18:13 ` checkpatch [this message]
2024-03-08 19:03 ` 0-day Robot
2024-03-08 22:27 ` |SUCCESS| pw138133 [PATCH] [v2] " dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:33 ` dpdklab
2024-03-08 22:43 ` dpdklab
2024-03-08 22:53 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 23:01 ` dpdklab
2024-03-08 23:02 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:07 ` dpdklab
2024-03-08 23:19 ` dpdklab
2024-03-08 23:20 ` dpdklab
2024-03-08 23:23 ` dpdklab
2024-03-08 23:26 ` dpdklab
2024-03-08 23:27 ` dpdklab
2024-03-08 23:27 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:54 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:58 ` dpdklab
2024-03-09 0:03 ` dpdklab
2024-03-09 0:03 ` dpdklab
2024-03-09 0:05 ` dpdklab
2024-03-09 0:05 ` dpdklab
2024-03-09 0:05 ` dpdklab
2024-03-09 0:05 ` dpdklab
2024-03-09 0:06 ` dpdklab
2024-03-09 0:06 ` dpdklab
2024-03-09 0:07 ` dpdklab
2024-03-09 0:07 ` dpdklab
2024-03-09 0:08 ` dpdklab
2024-03-09 0:10 ` dpdklab
2024-03-09 0:10 ` dpdklab
2024-03-09 0:10 ` dpdklab
2024-03-09 0:11 ` dpdklab
2024-03-09 0:11 ` dpdklab
2024-03-09 0:11 ` dpdklab
2024-03-09 0:11 ` dpdklab
2024-03-09 0:11 ` dpdklab
2024-03-09 0:12 ` dpdklab
2024-03-09 0:12 ` dpdklab
2024-03-09 0:12 ` dpdklab
2024-03-09 0:13 ` dpdklab
2024-03-09 0:14 ` dpdklab
2024-03-09 0:14 ` dpdklab
2024-03-09 0:14 ` dpdklab
2024-03-09 0:14 ` dpdklab
2024-03-09 0:15 ` dpdklab
2024-03-09 0:15 ` dpdklab
2024-03-09 0:15 ` dpdklab
2024-03-09 0:18 ` dpdklab
2024-03-09 0:18 ` dpdklab
2024-03-09 0:18 ` dpdklab
2024-03-09 0:20 ` dpdklab
2024-03-09 0:20 ` dpdklab
2024-03-09 0:23 ` dpdklab
2024-03-09 0:24 ` dpdklab
2024-03-09 0:50 ` dpdklab
2024-03-09 1:20 ` dpdklab
2024-03-09 1:41 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 17:47 ` 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=20240308181327.38EC71223EF@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).