From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: [BUG] ACL library using printf
Date: Mon, 8 Jan 2018 16:06:58 -0800
Message-ID: <20180108160658.4ce7f7a7@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f195.google.com (mail-pf0-f195.google.com
 [209.85.192.195]) by dpdk.org (Postfix) with ESMTP id 96D561B024
 for <dev@dpdk.org>; Tue,  9 Jan 2018 01:07:11 +0100 (CET)
Received: by mail-pf0-f195.google.com with SMTP id e3so7204636pfi.10
 for <dev@dpdk.org>; Mon, 08 Jan 2018 16:07:11 -0800 (PST)
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.