From: Stephen Hemminger <stephen@networkplumber.org>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [BUG] ACL library using printf
Date: Mon, 8 Jan 2018 16:06:58 -0800 [thread overview]
Message-ID: <20180108160658.4ce7f7a7@xeon-e3> (raw)
In general, DPDK functions must not print to stdout (or stderr) directly because
typically DPDK applications are run as daemons and console is redirected to /dev/null.
Doing a small audit of this noticed that ACL library needs to be fixed.
Instead of looking at log_level and using printf, it should be using
new dynamic logging and normal rte_log.
Please fix this.
reply other threads:[~2018-01-09 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180108160658.4ce7f7a7@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
/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).