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| pw138476 [PATCH v9 5/5] eal: add option to put timestamp on console output
Date: Mon, 18 Mar 2024 23:05:32 +0100 (CET)	[thread overview]
Message-ID: <20240318220532.5EEBC1223F7@dpdk.org> (raw)
In-Reply-To: <20240318220432.7486-6-stephen@networkplumber.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#95: 
This logging skips the unnecessary step of going through stdio,

total: 0 errors, 1 warnings, 179 lines checked
Warning in lib/log/log_unix.c:
Writing to stdout or stderr

  parent reply	other threads:[~2024-03-18 22:05 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318220432.7486-6-stephen@networkplumber.org>
2024-03-18 21:43 ` |SUCCESS| pw138472-138476 " qemudev
2024-03-18 21:47 ` |FAILURE| " qemudev
2024-03-18 22:05 ` checkpatch [this message]
2024-03-18 22:50 ` |SUCCESS| pw138472-138476 [PATCH] [v9,5/5] eal: add option to put ti dpdklab
2024-03-18 22:51 ` dpdklab
2024-03-18 22:51 ` dpdklab
2024-03-18 22:52 ` |FAILURE| " dpdklab
2024-03-18 22:52 ` |SUCCESS| " dpdklab
2024-03-18 22:52 ` |FAILURE| " dpdklab
2024-03-18 22:52 ` dpdklab
2024-03-18 22:52 ` |SUCCESS| " dpdklab
2024-03-18 22:53 ` |FAILURE| " dpdklab
2024-03-18 22:53 ` dpdklab
2024-03-18 22:53 ` dpdklab
2024-03-18 22:53 ` dpdklab
2024-03-18 22:57 ` dpdklab
2024-03-18 22:57 ` |SUCCESS| " dpdklab
2024-03-18 22:58 ` |FAILURE| " dpdklab
2024-03-18 22:58 ` dpdklab
2024-03-18 22:58 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` |SUCCESS| " dpdklab
2024-03-18 22:59 ` |FAILURE| " dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` |SUCCESS| " dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 22:59 ` dpdklab
2024-03-18 23:00 ` dpdklab
2024-03-18 23:00 ` |FAILURE| " dpdklab
2024-03-18 23:00 ` |SUCCESS| " dpdklab
2024-03-18 23:00 ` |FAILURE| " dpdklab
2024-03-18 23:00 ` |SUCCESS| " dpdklab
2024-03-18 23:00 ` |FAILURE| " dpdklab
2024-03-18 23:00 ` |SUCCESS| " dpdklab
2024-03-18 23:00 ` dpdklab
2024-03-18 23:00 ` dpdklab
2024-03-18 23:01 ` dpdklab
2024-03-18 23:01 ` dpdklab
2024-03-18 23:01 ` dpdklab
2024-03-18 23:02 ` |FAILURE| " dpdklab
2024-03-18 23:03 ` dpdklab
2024-03-18 23:03 ` dpdklab
2024-03-18 23:03 ` |FAILURE| pw138476 [PATCH v9 5/5] eal: add option to put timestamp on console output 0-day Robot
2024-03-18 23:04 ` |FAILURE| pw138472-138476 [PATCH] [v9,5/5] eal: add option to put ti dpdklab
2024-03-18 23:04 ` |SUCCESS| " dpdklab
2024-03-18 23:04 ` dpdklab
2024-03-18 23:04 ` dpdklab
2024-03-18 23:04 ` dpdklab
2024-03-18 23:05 ` dpdklab
2024-03-18 23:05 ` dpdklab
2024-03-18 23:05 ` dpdklab
2024-03-18 23:05 ` |FAILURE| " dpdklab
2024-03-18 23:05 ` |SUCCESS| " dpdklab
2024-03-18 23:06 ` |FAILURE| " dpdklab
2024-03-18 23:06 ` |SUCCESS| " dpdklab
2024-03-18 23:06 ` dpdklab
2024-03-18 23:06 ` |FAILURE| " dpdklab
2024-03-18 23:06 ` dpdklab
2024-03-18 23:07 ` |SUCCESS| " dpdklab
2024-03-18 23:08 ` |FAILURE| " dpdklab
2024-03-18 23:08 ` |SUCCESS| " dpdklab
2024-03-18 23:24 ` |FAILURE| " dpdklab
2024-03-18 23:24 ` |SUCCESS| " dpdklab
2024-03-18 23:25 ` dpdklab
2024-03-18 23:27 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:31 ` |FAILURE| " dpdklab
2024-03-18 23:31 ` |SUCCESS| " dpdklab
2024-03-19  0:10 ` dpdklab
2024-03-20 20:50 ` dpdklab
2024-03-20 21:44 ` 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=20240318220532.5EEBC1223F7@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).