From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |WARNING| pw60078 [PATCH v2 2/2] build: support building ABI versioned files twice
Date: Fri, 27 Sep 2019 23:01:15 +0200 (CEST) [thread overview]
Message-ID: <20190927210115.2352A1BF0D@dpdk.org> (raw)
In-Reply-To: <20190927205931.23022-3-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/60078
_coding style issues_
WARNING:TYPO_SPELLING: 'accomodate' may be misspelled - perhaps 'accommodate'?
#21:
static builds, so we need to accomodate that. Rather than building
WARNING:LONG_LINE: line over 90 characters
#107: FILE: lib/librte_eal/common/include/rte_function_versioning.h:11:
+#error Use of function versioning disabled, is "use_function_versioning=true" in meson.build?
total: 0 errors, 2 warnings, 85 lines checked
parent reply other threads:[~2019-09-27 21:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190927205931.23022-3-bruce.richardson@intel.com>]
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=20190927210115.2352A1BF0D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@intel.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).