From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wojciech Panfil <wojciech.panfil@intel.com>
Subject: |WARNING| pw144184 [PATCH] eal/alarm_cancel: Fix thread starvation
Date: Wed, 18 Sep 2024 08:56:13 +0200 (CEST) [thread overview]
Message-ID: <20240918065613.EB412121D10@dpdk.org> (raw)
In-Reply-To: <20240918070212.10339-1-wojciech.panfil@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/144184
_coding style issues_
WARNING:LONG_LINE_COMMENT: line length of 105 exceeds 100 columns
#175: FILE: lib/eal/freebsd/eal_alarm.c:324:
+ /* Yield control to a second thread executing eal_alarm_callback to avoid its starvation,
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#176: FILE: lib/eal/freebsd/eal_alarm.c:325:
+ * as it is waiting for the lock we have just released. */
WARNING:LONG_LINE_COMMENT: line length of 105 exceeds 100 columns
#192: FILE: lib/eal/linux/eal_alarm.c:254:
+ /* Yield control to a second thread executing eal_alarm_callback to avoid its starvation,
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#193: FILE: lib/eal/linux/eal_alarm.c:255:
+ * as it is waiting for the lock we have just released. */
WARNING:LONG_LINE_COMMENT: line length of 105 exceeds 100 columns
#207: FILE: lib/eal/windows/eal_alarm.c:215:
+ /* Yield control to a second thread executing eal_alarm_callback to avoid its starvation,
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#208: FILE: lib/eal/windows/eal_alarm.c:216:
+ * as it is waiting for the lock we have just released. */
total: 0 errors, 6 warnings, 34 lines checked
next prev parent reply other threads:[~2024-09-18 6:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240918070212.10339-1-wojciech.panfil@intel.com>
2024-09-18 6:27 ` |SUCCESS| " qemudev
2024-09-18 6:32 ` qemudev
2024-09-18 6:56 ` checkpatch [this message]
2024-09-18 7:44 ` 0-day Robot
2024-09-18 12:34 ` dpdklab
2024-09-18 12:46 ` dpdklab
2024-09-18 12:47 ` dpdklab
2024-09-18 13:06 ` dpdklab
2024-09-18 13:08 ` dpdklab
2024-09-18 14:53 ` dpdklab
2024-09-18 15:08 ` |PENDING| " dpdklab
2024-09-18 15:51 ` |SUCCESS| " dpdklab
2024-09-18 16:02 ` dpdklab
2024-09-18 16:03 ` dpdklab
2024-09-18 16:31 ` dpdklab
2024-09-18 17:33 ` dpdklab
2024-09-19 8:50 ` 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=20240918065613.EB412121D10@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wojciech.panfil@intel.com \
/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).