From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: |WARNING| pw143250 [PATCH v19 5/5] dts: add API doc generation
Date: Wed, 21 Aug 2024 17:05:01 +0200 (CEST) [thread overview]
Message-ID: <20240821150501.8F143123EF6@dpdk.org> (raw)
In-Reply-To: <20240821150254.158912-6-juraj.linkes@pantheon.tech>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143250
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#110:
[0] https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings
total: 0 errors, 1 warnings, 313 lines checked
next prev parent reply other threads:[~2024-08-21 15:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240821150254.158912-6-juraj.linkes@pantheon.tech>
2024-08-21 14:37 ` |SUCCESS| pw143246-143250 " qemudev
2024-08-21 14:41 ` qemudev
2024-08-21 15:05 ` checkpatch [this message]
2024-08-21 16:03 ` |SUCCESS| pw143250 " 0-day Robot
2024-08-21 22:04 ` |SUCCESS| pw143246-143250 [PATCH] [v19,5/5] dts: add API doc generat dpdklab
2024-08-21 22:09 ` dpdklab
2024-08-21 22:22 ` dpdklab
2024-08-21 22:28 ` dpdklab
2024-08-21 22:31 ` dpdklab
2024-08-21 22:38 ` |PENDING| " dpdklab
2024-08-21 22:45 ` |SUCCESS| " dpdklab
2024-08-21 23:02 ` dpdklab
2024-08-21 23:13 ` |PENDING| " dpdklab
2024-08-21 23:28 ` |SUCCESS| " dpdklab
2024-08-21 23:32 ` |PENDING| " dpdklab
2024-08-22 0:02 ` |SUCCESS| " dpdklab
2024-08-22 0:02 ` dpdklab
2024-08-22 0:03 ` dpdklab
2024-08-22 0:03 ` dpdklab
2024-08-22 0:05 ` dpdklab
2024-08-22 0:37 ` dpdklab
2024-08-22 0:41 ` dpdklab
2024-08-22 0:53 ` dpdklab
2024-08-22 1:14 ` dpdklab
2024-08-22 1:19 ` dpdklab
2024-08-22 1:27 ` dpdklab
2024-08-22 1:28 ` dpdklab
2024-08-22 2:09 ` dpdklab
2024-08-22 2:10 ` dpdklab
2024-08-22 2:10 ` dpdklab
2024-08-22 3:09 ` dpdklab
2024-08-22 6:46 ` 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=20240821150501.8F143123EF6@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--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).