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| pw139605 [RFC] fix semicolon at the end of RTE_LOG_REGISTER_DEFAULT
Date: Sat, 20 Apr 2024 02:09:20 +0200 (CEST)	[thread overview]
Message-ID: <20240420000920.99D5D124858@dpdk.org> (raw)
In-Reply-To: <20240420000827.192451-1-stephen@networkplumber.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#469: FILE: drivers/common/cnxk/roc_platform.c:96:
+RTE_LOG_REGISTER_DEFAULT(cnxk_logtype_tim, NOTICE)

total: 0 errors, 1 warnings, 744 lines checked

       reply	other threads:[~2024-04-20  0:09 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240420000827.192451-1-stephen@networkplumber.org>
2024-04-20  0:09 ` checkpatch [this message]
2024-04-20  1:04 ` |SUCCESS| " 0-day Robot
2024-04-22  1:47 ` qemudev
2024-04-22  1:52 ` qemudev
2024-04-22  8:10 ` |SUCCESS| pw139605 [PATCH] [RFC] fix semicolon at the end of RTE_LOG dpdklab
2024-04-22  8:11 ` dpdklab
2024-04-22  8:14 ` dpdklab
2024-04-22  8:18 ` dpdklab
2024-04-22  8:22 ` dpdklab
2024-04-22  8:25 ` dpdklab
2024-04-22  8:27 ` dpdklab
2024-04-22  8:28 ` dpdklab
2024-04-22  8:33 ` dpdklab
2024-04-22  8:33 ` dpdklab
2024-04-22  8:34 ` dpdklab
2024-04-22  8:34 ` dpdklab
2024-04-22  8:34 ` dpdklab
2024-04-22  8:56 ` dpdklab
2024-04-22  8:58 ` dpdklab
2024-04-22  9:00 ` dpdklab
2024-04-22  9:00 ` dpdklab
2024-04-22  9:01 ` dpdklab
2024-04-22  9:01 ` dpdklab
2024-04-22  9:03 ` dpdklab
2024-04-22  9:04 ` dpdklab
2024-04-22  9:05 ` dpdklab
2024-04-22  9:06 ` dpdklab
2024-04-22  9:06 ` dpdklab
2024-04-22  9:07 ` dpdklab
2024-04-22  9:07 ` dpdklab
2024-04-22  9:07 ` dpdklab
2024-04-22  9:08 ` dpdklab
2024-04-22  9:08 ` dpdklab
2024-04-22  9:08 ` dpdklab
2024-04-22  9:08 ` dpdklab
2024-04-22  9:09 ` dpdklab
2024-04-22  9:09 ` dpdklab
2024-04-22  9:09 ` dpdklab
2024-04-22  9:10 ` dpdklab
2024-04-22  9:10 ` dpdklab
2024-04-22  9:10 ` dpdklab
2024-04-22  9:11 ` dpdklab
2024-04-22  9:11 ` dpdklab
2024-04-22  9:11 ` dpdklab
2024-04-22  9:11 ` dpdklab
2024-04-22  9:12 ` dpdklab
2024-04-22  9:12 ` dpdklab
2024-04-22  9:12 ` dpdklab
2024-04-22  9:12 ` dpdklab
2024-04-22  9:12 ` dpdklab
2024-04-22  9:12 ` dpdklab
2024-04-22  9:13 ` dpdklab
2024-04-22  9:13 ` dpdklab
2024-04-22  9:13 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:14 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:15 ` dpdklab
2024-04-22  9:16 ` dpdklab
2024-04-22  9:16 ` dpdklab
2024-04-22  9:16 ` dpdklab
2024-04-22  9:16 ` dpdklab
2024-04-22  9:16 ` dpdklab
2024-04-22  9:16 ` dpdklab
2024-04-22  9:17 ` dpdklab
2024-04-22  9:19 ` dpdklab
2024-04-22  9:19 ` dpdklab
2024-04-22  9:23 ` dpdklab
2024-04-22  9:23 ` dpdklab
2024-04-22  9:24 ` dpdklab
2024-04-22  9:28 ` dpdklab
2024-04-22  9:30 ` dpdklab
2024-04-22  9:31 ` dpdklab
2024-04-22  9:32 ` dpdklab
2024-04-22  9:50 ` dpdklab
2024-04-22 10:15 ` dpdklab
2024-04-22 10:18 ` dpdklab
2024-04-22 10:51 ` 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=20240420000920.99D5D124858@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).