From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw147879 [PATCH] eal/unix: optimize thread creation with glibc
Date: Sat, 2 Nov 2024 11:10:57 +0100 (CET) [thread overview]
Message-ID: <20241102101057.9EEDD12314F@dpdk.org> (raw)
In-Reply-To: <20241102100839.2325651-1-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/147879
_coding style issues_
WARNING:TYPO_SPELLING: 'musl' may be misspelled - perhaps 'must'?
#83:
pthread_attr_setaffinity_np, but it is not available with musl.
WARNING:TYPO_SPELLING: 'musl' may be misspelled - perhaps 'must'?
#84:
Assume availability by relying on __USE_GNU that is not set with musl.
total: 0 errors, 2 warnings, 86 lines checked
Warning in lib/eal/unix/rte_thread.c:
Using pthread functions, prefer rte_thread
next prev parent reply other threads:[~2024-11-02 10:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241102100839.2325651-1-david.marchand@redhat.com>
2024-11-02 9:45 ` |SUCCESS| " qemudev
2024-11-02 9:49 ` qemudev
2024-11-02 10:10 ` checkpatch [this message]
2024-11-02 10:44 ` |PENDING| pw147879 [PATCH] eal/unix: optimize thread creation with g dpdklab
2024-11-02 10:45 ` dpdklab
2024-11-02 10:52 ` |SUCCESS| " dpdklab
2024-11-02 10:55 ` dpdklab
2024-11-02 11:02 ` dpdklab
2024-11-02 11:04 ` |SUCCESS| pw147879 [PATCH] eal/unix: optimize thread creation with glibc 0-day Robot
2024-11-02 11:05 ` |SUCCESS| pw147879 [PATCH] eal/unix: optimize thread creation with g dpdklab
2024-11-02 11:07 ` dpdklab
2024-11-02 11:07 ` dpdklab
2024-11-02 11:14 ` dpdklab
2024-11-02 11:30 ` dpdklab
2024-11-02 12:06 ` |FAILURE| " dpdklab
2024-11-02 12:39 ` |SUCCESS| " 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=20241102101057.9EEDD12314F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.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).