From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nandini Persad <nandinipersad361@gmail.com>
Subject: |WARNING| pw141472 [PATCH v2 9/9] doc: reword rcu library section in prog guide
Date: Fri, 21 Jun 2024 04:34:44 +0200 (CEST) [thread overview]
Message-ID: <20240621023444.E150A128144@dpdk.org> (raw)
In-Reply-To: <20240621023254.4258-9-nandinipersad361@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141472
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#82:
Simple syntax changes made to the rcu library section in programmer's guide.
total: 0 errors, 1 warnings, 172 lines checked
next prev parent reply other threads:[~2024-06-21 2:34 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240621023254.4258-9-nandinipersad361@gmail.com>
2024-06-21 2:10 ` |SUCCESS| pw141464-141472 " qemudev
2024-06-21 2:15 ` qemudev
2024-06-21 2:34 ` checkpatch [this message]
2024-06-21 3:25 ` |SUCCESS| pw141472 " 0-day Robot
2024-06-21 13:44 ` |SUCCESS| pw141464-141472 [PATCH] [v2,9/9] doc: reword rcu library s dpdklab
2024-06-21 13:51 ` dpdklab
2024-06-21 13:52 ` dpdklab
2024-06-21 13:55 ` dpdklab
2024-06-21 13:55 ` dpdklab
2024-06-21 13:56 ` dpdklab
2024-06-21 13:57 ` dpdklab
2024-06-21 13:58 ` dpdklab
2024-06-21 13:58 ` dpdklab
2024-06-21 13:59 ` dpdklab
2024-06-21 14:00 ` dpdklab
2024-06-21 14:01 ` dpdklab
2024-06-21 14:01 ` dpdklab
2024-06-21 14:04 ` dpdklab
2024-06-21 14:05 ` dpdklab
2024-06-21 14:06 ` dpdklab
2024-06-21 14:07 ` dpdklab
2024-06-21 14:09 ` dpdklab
2024-06-21 14:09 ` dpdklab
2024-06-21 14:09 ` dpdklab
2024-06-21 14:11 ` dpdklab
2024-06-21 14:12 ` dpdklab
2024-06-21 14:17 ` dpdklab
2024-06-21 14:18 ` dpdklab
2024-06-21 14:20 ` dpdklab
2024-06-21 14:21 ` dpdklab
2024-06-21 14:24 ` dpdklab
2024-06-21 14:25 ` dpdklab
2024-06-21 14:30 ` dpdklab
2024-06-21 14:30 ` dpdklab
2024-06-21 14:35 ` dpdklab
2024-06-21 14:47 ` dpdklab
2024-06-21 14:49 ` dpdklab
2024-06-21 14:51 ` dpdklab
2024-06-21 14:53 ` dpdklab
2024-06-21 14:56 ` dpdklab
2024-06-21 14:57 ` dpdklab
2024-06-21 15:01 ` dpdklab
2024-06-21 15:04 ` dpdklab
2024-06-21 15:06 ` dpdklab
2024-06-21 15:10 ` dpdklab
2024-06-21 15:11 ` dpdklab
2024-06-21 15:14 ` dpdklab
2024-06-21 15:14 ` dpdklab
2024-06-21 15:17 ` dpdklab
2024-06-21 15:17 ` dpdklab
2024-06-21 15:17 ` dpdklab
2024-06-21 15:18 ` dpdklab
2024-06-21 15:18 ` dpdklab
2024-06-21 15:19 ` dpdklab
2024-06-21 15:19 ` dpdklab
2024-06-21 15:19 ` dpdklab
2024-06-21 15:20 ` dpdklab
2024-06-21 15:21 ` dpdklab
2024-06-21 15:21 ` dpdklab
2024-06-21 15:22 ` dpdklab
2024-06-21 15:22 ` dpdklab
2024-06-21 15:22 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:23 ` dpdklab
2024-06-21 15:24 ` dpdklab
2024-06-21 15:24 ` dpdklab
2024-06-21 15:24 ` dpdklab
2024-06-21 15:24 ` dpdklab
2024-06-21 15:25 ` dpdklab
2024-06-21 15:25 ` dpdklab
2024-06-21 15:26 ` dpdklab
2024-06-21 15:26 ` dpdklab
2024-06-21 15:26 ` dpdklab
2024-06-21 15:27 ` dpdklab
2024-06-21 15:27 ` dpdklab
2024-06-21 15:28 ` dpdklab
2024-06-21 15:28 ` dpdklab
2024-06-21 15:28 ` dpdklab
2024-06-21 15:28 ` dpdklab
2024-06-21 15:29 ` dpdklab
2024-06-21 15:29 ` dpdklab
2024-06-21 15:30 ` dpdklab
2024-06-21 15:30 ` dpdklab
2024-06-21 15:31 ` dpdklab
2024-06-21 15:31 ` dpdklab
2024-06-21 15:31 ` dpdklab
2024-06-21 15:32 ` dpdklab
2024-06-21 15:32 ` dpdklab
2024-06-21 15:33 ` dpdklab
2024-06-21 15:36 ` dpdklab
2024-06-21 15:42 ` dpdklab
2024-06-21 15:42 ` dpdklab
2024-06-21 15:47 ` dpdklab
2024-06-21 15:47 ` dpdklab
2024-06-21 16:02 ` dpdklab
2024-06-21 16:04 ` dpdklab
2024-06-21 16:56 ` dpdklab
2024-06-21 17:28 ` dpdklab
2024-06-21 21:00 ` dpdklab
2024-06-21 21:14 ` dpdklab
2024-06-22 12:29 ` 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=20240621023444.E150A128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nandinipersad361@gmail.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).