From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Piotr Kubaj <pkubaj@FreeBSD.org>
Subject: [dpdk-test-report] |WARNING| pw89073 [PATCH] ppc64le: fix build with Clang and without glibc
Date: Sun, 14 Mar 2021 11:07:18 +0100 (CET) [thread overview]
Message-ID: <20210314100718.F1DDF3DC@dpdk.org> (raw)
In-Reply-To: <20210311161140.70534-1-pkubaj@FreeBSD.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89073
_coding style issues_
WARNING:TYPO_SPELLING: 'dependant' may be misspelled - perhaps 'dependent'?
#59:
3. Additionally, sys/platform/ppc.h is glibc-dependant and is not
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#62:
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/powerpc/sys/platform/ppc.h
CHECK:ARCH_DEFINES: architecture specific defines should be avoided
#128: FILE: drivers/net/bnxt/bnxt_irq.h:11:
+#if defined(__clang__) && defined(__powerpc64__)
CHECK:ARCH_DEFINES: architecture specific defines should be avoided
#345: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:5600:
+#if defined(__clang__) && defined(__powerpc64__)
CHECK:ARCH_DEFINES: architecture specific defines should be avoided
#359: FILE: drivers/net/ixgbe/ixgbe_rxtx.c:4743:
+#if defined(__clang__) && defined(__powerpc64__)
CHECK:ARCH_DEFINES: architecture specific defines should be avoided
#373: FILE: drivers/net/txgbe/txgbe_ethdev.c:3385:
+#if defined(__clang__) && defined(__powerpc64__)
total: 0 errors, 2 warnings, 279 lines checked
parent reply other threads:[~2021-03-14 10:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210311161140.70534-1-pkubaj@FreeBSD.org>]
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=20210314100718.F1DDF3DC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pkubaj@FreeBSD.org \
--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).