automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw141157 [PATCH v10] examples/ptp: replace terms master and slave
Date: Fri, 14 Jun 2024 17:48:14 +0200 (CEST)	[thread overview]
Message-ID: <20240614154814.81484124124@dpdk.org> (raw)
In-Reply-To: <20240614154615.65507-1-stephen@networkplumber.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141157

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#67: 
Subject: [PATCH v10] examples/ptp: replace terms master and slave

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#67: 
Subject: [PATCH v10] examples/ptp: replace terms master and slave

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#87: 
Remove one of the few remaining uses of master/slave.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#87: 
Remove one of the few remaining uses of master/slave.

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#90: 
of master-slave terminology. Change the sample to Use the terms

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#90: 
of master-slave terminology. Change the sample to Use the terms

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#93: 
  In place of the term “master”, use the term “timeTransmitter”.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#94: 
  In place of the term “slave”, use the term “timeReceiver”.

total: 0 errors, 8 warnings, 254 lines checked

  parent reply	other threads:[~2024-06-14 15:48 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240614154615.65507-1-stephen@networkplumber.org>
2024-06-14 15:19 ` |SUCCESS| " qemudev
2024-06-14 15:24 ` qemudev
2024-06-14 15:48 ` checkpatch [this message]
2024-06-14 16:44 ` 0-day Robot
2024-06-14 20:58 ` |SUCCESS| pw141157 [PATCH] [v10] examples/ptp: replace terms master dpdklab
2024-06-14 21:12 ` dpdklab
2024-06-14 21:13 ` dpdklab
2024-06-14 21:43 ` dpdklab
2024-06-14 21:48 ` dpdklab
2024-06-14 21:50 ` dpdklab
2024-06-14 21:50 ` dpdklab
2024-06-14 21:52 ` dpdklab
2024-06-14 21:52 ` dpdklab
2024-06-14 21:52 ` dpdklab
2024-06-14 21:57 ` dpdklab
2024-06-14 21:58 ` dpdklab
2024-06-14 21:59 ` dpdklab
2024-06-14 22:01 ` dpdklab
2024-06-14 22:01 ` dpdklab
2024-06-14 22:02 ` dpdklab
2024-06-14 22:03 ` dpdklab
2024-06-14 22:03 ` dpdklab
2024-06-14 22:03 ` dpdklab
2024-06-14 22:08 ` dpdklab
2024-06-14 22:08 ` dpdklab
2024-06-14 22:09 ` dpdklab
2024-06-14 22:10 ` dpdklab
2024-06-14 22:10 ` dpdklab
2024-06-14 22:11 ` dpdklab
2024-06-14 22:11 ` dpdklab
2024-06-14 22:11 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:13 ` dpdklab
2024-06-14 22:13 ` dpdklab
2024-06-14 22:14 ` dpdklab
2024-06-14 22:14 ` dpdklab
2024-06-14 22:14 ` dpdklab
2024-06-14 22:15 ` dpdklab
2024-06-14 22:18 ` dpdklab
2024-06-14 22:19 ` dpdklab
2024-06-14 22:19 ` dpdklab
2024-06-14 22:20 ` dpdklab
2024-06-14 22:20 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:22 ` dpdklab
2024-06-14 22:22 ` dpdklab
2024-06-14 22:22 ` dpdklab
2024-06-14 22:23 ` dpdklab
2024-06-14 22:23 ` dpdklab
2024-06-14 22:24 ` dpdklab
2024-06-14 22:25 ` dpdklab
2024-06-14 22:25 ` dpdklab
2024-06-14 22:26 ` dpdklab
2024-06-14 22:26 ` dpdklab
2024-06-14 22:32 ` dpdklab
2024-06-14 22:53 ` dpdklab
2024-06-14 22:54 ` dpdklab
2024-06-14 22:55 ` dpdklab
2024-06-14 22:55 ` dpdklab
2024-06-14 22:56 ` dpdklab
2024-06-14 22:56 ` dpdklab
2024-06-14 22:57 ` dpdklab
2024-06-14 22:57 ` dpdklab
2024-06-14 22:58 ` dpdklab
2024-06-14 22:58 ` dpdklab
2024-06-14 23:01 ` dpdklab
2024-06-14 23:03 ` dpdklab
2024-06-14 23:04 ` dpdklab
2024-06-14 23:04 ` dpdklab
2024-06-14 23:06 ` dpdklab
2024-06-14 23:07 ` dpdklab
2024-06-14 23:07 ` dpdklab
2024-06-14 23:08 ` dpdklab
2024-06-14 23:09 ` dpdklab
2024-06-14 23:10 ` dpdklab
2024-06-14 23:10 ` dpdklab
2024-06-14 23:10 ` dpdklab
2024-06-14 23:11 ` dpdklab
2024-06-14 23:19 ` dpdklab
2024-06-14 23:19 ` dpdklab
2024-06-14 23:20 ` dpdklab
2024-06-14 23:20 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:22 ` dpdklab
2024-06-14 23:22 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:24 ` dpdklab
2024-06-14 23:24 ` dpdklab
2024-06-14 23:25 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:49 ` dpdklab
2024-06-14 23:49 ` dpdklab
2024-06-14 23:50 ` dpdklab
2024-06-15  0:00 ` dpdklab
2024-06-15  0:03 ` dpdklab
2024-06-15  0:08 ` 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=20240614154814.81484124124@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).