From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Artur Trybula <arturx.trybula@intel.com>
Subject: [dpdk-test-report] |WARNING| pw63939 [PATCH] eal: improve user notification for too low memzone segments
Date: Mon, 16 Dec 2019 16:56:52 +0100 (CET) [thread overview]
Message-ID: <20191216155652.D76112B96@dpdk.org> (raw)
In-Reply-To: <20191216154406.3827-1-arturx.trybula@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/63939
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#70: FILE: lib/librte_eal/common/eal_common_memzone.c:74:
+ RTE_LOG(ERR, EAL, "%s(): Number of requested memzone segments exceeds RTE_MAX_MEMZONE
", __func__);
total: 0 errors, 1 warnings, 8 lines checked
next parent reply other threads:[~2019-12-16 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191216154406.3827-1-arturx.trybula@intel.com>
2019-12-16 15:56 ` checkpatch [this message]
2019-12-16 21:55 ` [dpdk-test-report] |WARNING| pw63939 " 0-day Robot
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=20191216155652.D76112B96@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arturx.trybula@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).