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| pw134701 [PATCH v2] examples/ptp: replace terms master and slave
Date: Wed, 29 Nov 2023 17:45:55 +0100 (CET)	[thread overview]
Message-ID: <20231129164555.C3201120787@dpdk.org> (raw)
In-Reply-To: <20231129164438.67237-1-stephen@networkplumber.org>

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

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

_coding style issues_


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

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

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#88: 
of master-slave terminolgy. Use the terms recommended by

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#88: 
of master-slave terminolgy. Use the terms recommended by

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

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

total: 0 errors, 6 warnings, 256 lines checked

  parent reply	other threads:[~2023-11-29 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231129164438.67237-1-stephen@networkplumber.org>
2023-11-29 16:26 ` |SUCCESS| " qemudev
2023-11-29 16:30 ` qemudev
2023-11-29 16:45 ` checkpatch [this message]
2023-11-29 17:38 ` 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=20231129164555.C3201120787@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).