automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <changqing.li@windriver.com>
Subject: |WARNING| pw153181 [PATCH] Add new tracepoint function for type time_t
Date: Tue, 29 Apr 2025 05:00:28 +0200 (CEST)	[thread overview]
Message-ID: <20250429030028.9C537123FA7@dpdk.org> (raw)
In-Reply-To: <20250429030017.1126516-1-changqing.li@windriver.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#88: 
  498 | #define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))

total: 0 errors, 1 warnings, 54 lines checked

  parent reply	other threads:[~2025-04-29  3:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250429030017.1126516-1-changqing.li@windriver.com>
2025-04-29  2:27 ` |SUCCESS| " qemudev
2025-04-29  2:31 ` qemudev
2025-04-29  3:00 ` checkpatch [this message]
2025-04-29  3:26 ` |SUCCESS| pw153181 [PATCH] Add new tracepoint function for type time dpdklab
2025-04-29  3:30 ` dpdklab
2025-04-29  3:43 ` |PENDING| " dpdklab
2025-04-29  3:45 ` |SUCCESS| " dpdklab
2025-04-29  3:47 ` dpdklab
2025-04-29  3:48 ` |PENDING| " dpdklab
2025-04-29  3:50 ` |SUCCESS| " dpdklab
2025-04-29  3:52 ` |PENDING| " dpdklab
2025-04-29  3:55 ` |SUCCESS| " dpdklab
2025-04-29  4:01 ` dpdklab
2025-04-29  4:04 ` |FAILURE| pw153181 [PATCH] Add new tracepoint function for type time_t 0-day Robot
2025-04-29  4:07 ` |PENDING| pw153181 [PATCH] Add new tracepoint function for type time dpdklab
2025-04-29  4:10 ` |SUCCESS| " dpdklab
2025-04-29  4:11 ` |PENDING| " dpdklab
2025-04-29  4:34 ` |SUCCESS| " dpdklab
2025-04-29  4:59 ` dpdklab
2025-04-29  5:01 ` dpdklab
2025-04-29  5:34 ` dpdklab
2025-04-29  6:55 ` dpdklab
2025-04-29  8:18 ` 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=20250429030028.9C537123FA7@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=changqing.li@windriver.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).