automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mingjin Ye <mingjinx.ye@intel.com>
Subject: |WARNING| pw143686 [PATCH v2 3/3] examples/ptpclient: add frequency adjustment support
Date: Fri,  6 Sep 2024 07:44:07 +0200 (CEST)	[thread overview]
Message-ID: <20240906054407.75D7A121D10@dpdk.org> (raw)
In-Reply-To: <20240906051939.879071-4-mingjinx.ye@intel.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#128: FILE: examples/ptpclient/ptpclient.c:167:
+	int64_t master_offset;

WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#139: FILE: examples/ptpclient/ptpclient.c:328:
+	printf("
T4 - Master Clock.  %lds %ldns
",

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#145: FILE: examples/ptpclient/ptpclient.c:333:
+		printf("
Delta between master and slave clocks:%"PRId64"ns
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#145: FILE: examples/ptpclient/ptpclient.c:333:
+		printf("
Delta between master and slave clocks:%"PRId64"ns
",

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#189: FILE: examples/ptpclient/ptpclient.c:364:
+		printf("master offset: %"PRId64"ns
", ptp_data->master_offset);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#189: FILE: examples/ptpclient/ptpclient.c:364:
+		printf("master offset: %"PRId64"ns
", ptp_data->master_offset);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#313: FILE: examples/ptpclient/ptpclient.c:542:
+ptp_adjust_freq(struct ptpv2_data_slave_ordinary *ptp_data)

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#321: FILE: examples/ptpclient/ptpclient.c:550:
+	ptp_data->master_offset = t2_ns - t1_ns - ptp_data->path_delay;

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#325: FILE: examples/ptpclient/ptpclient.c:554:
+	adj_freq = pi_sample(ptp_data->servo, ptp_data->master_offset, t2_ns,

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#336: FILE: examples/ptpclient/ptpclient.c:565:
+					     -ptp_data->master_offset);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#347: FILE: examples/ptpclient/ptpclient.c:576:
+send_delay_request(struct ptpv2_data_slave_ordinary *ptp_data)

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#387: FILE: examples/ptpclient/ptpclient.c:706:
+clock_path_delay(struct ptpv2_data_slave_ordinary *ptp_data)

total: 0 errors, 12 warnings, 412 lines checked

  parent reply	other threads:[~2024-09-06  5:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906051939.879071-4-mingjinx.ye@intel.com>
2024-09-06  5:17 ` |SUCCESS| pw143684-143686 " qemudev
2024-09-06  5:21 ` qemudev
2024-09-06  5:44 ` checkpatch [this message]
2024-09-06  6:44 ` |SUCCESS| pw143686 " 0-day Robot
2024-09-06 15:08 ` |SUCCESS| pw143684-143686 [PATCH] [v2,3/3] examples/ptpclient: add f dpdklab
2024-09-06 15:08 ` |PENDING| " dpdklab
2024-09-06 15:11 ` dpdklab
2024-09-06 15:18 ` |SUCCESS| " dpdklab
2024-09-06 15:18 ` dpdklab
2024-09-06 15:19 ` dpdklab
2024-09-06 16:22 ` dpdklab
2024-09-06 21:19 ` dpdklab
2024-09-06 21:20 ` dpdklab
2024-09-06 21:21 ` dpdklab
2024-09-06 21:21 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:23 ` dpdklab
2024-09-07  0:10 ` dpdklab
2024-09-07  0:14 ` dpdklab
2024-09-07  0:18 ` dpdklab
2024-09-07  0:38 ` dpdklab
2024-09-07  1:03 ` dpdklab
2024-09-07  4:10 ` dpdklab
2024-09-07  5:29 ` |PENDING| " dpdklab
2024-09-07  8:24 ` |SUCCESS| " dpdklab
2024-09-07 17:29 ` dpdklab
2024-09-08  1:42 ` dpdklab
2024-09-17  9:33 ` dpdklab
2024-09-17  9:54 ` 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=20240906054407.75D7A121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=mingjinx.ye@intel.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).