From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Min Zhou <zhoumin@loongson.cn>
Subject: |WARNING| pw117321 [PATCH v8 1/6] eal/loongarch: support LoongArch architecture
Date: Tue, 4 Oct 2022 17:53:26 +0200 (CEST) [thread overview]
Message-ID: <20221004155326.442B6120EFA@dpdk.org> (raw)
In-Reply-To: <20221004154047.35276-2-zhoumin@loongson.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/117321
_coding style issues_
WARNING:REPEATED_WORD: Possible repeated word: 'build'
#282: FILE: devtools/test-meson-builds.sh:265:
+build build-loongarch64-generic-gcc $f ABI $use_shared
WARNING:REPEATED_WORD: Possible repeated word: 'gcc'
#364: FILE: doc/guides/linux_gsg/cross_build_dpdk_for_loongarch.rst:59:
+ dnf install bison diffutils file flex gcc gcc-c++ git gmp-devel libtool make python3 rsync texinfo wget xz zlib-devel ccache
WARNING:SINGLE_STATEMENT_DO_WHILE_MACRO: Single statement macros should not use a do {} while (0) loop
#613: FILE: lib/eal/loongarch/include/rte_atomic.h:19:
+#define rte_mb() do { asm volatile("dbar 0":::"memory"); } while (0)
total: 0 errors, 3 warnings, 1069 lines checked
Warning in lib/eal/loongarch/include/rte_atomic.h:
Using rte_smp_[r/w]mb
Warning in lib/eal/loongarch/include/rte_atomic.h:
Using __atomic_thread_fence
parent reply other threads:[~2022-10-04 15:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221004154047.35276-2-zhoumin@loongson.cn>]
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=20221004155326.442B6120EFA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).