From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 9D4942B84
 for <dev@dpdk.org>; Thu, 20 Apr 2017 22:06:03 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 2A4D521BFB;
 Thu, 20 Apr 2017 16:06:03 -0400 (EDT)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Thu, 20 Apr 2017 16:06:03 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=ko8lal6KqUQdngS
 lWsTlfdNINd43GQ2zR95s4nAVarw=; b=MzxguOUDE8PVChOvWGlqkmkAWU/6FR8
 WaVIxT9Vtnvf4t6Fk5a7oL8lhd5ZuVcDEgZFpLnYkExTzownsmsX7UzDCP+nYJ4X
 gvk8kIUyVZEntS25Bxq5IjKkpYk2g8Onf9FNneGyw/VDvnvxMiMwaKUCiaWalbG1
 LerhU+hXtOQ4=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=
 fm1; bh=ko8lal6KqUQdngSlWsTlfdNINd43GQ2zR95s4nAVarw=; b=TOiESXFe
 J27DGNypdOsJznWeYcQPt6qk6UTawYt8CJ4Bf7HdCU5tg6k/kNljBEURtrjmTQK9
 gDWQK8TjYE3CN+XaFk4YnJ5o2hg6fwDI7nMmt2Nvfk+bfWv6F8N3AZx6clc0osCg
 knEkxcRUyg/q5raChxjzcgvJ0xlBKKe3Xpf8AAz6Z7socml0MeGs63mHW+pWdrG1
 E7kT5zx5zssc17PqmJs2Wv9RlvZVxgywDByM0STVb7XcSciyo1cXcYkMM65TWmDY
 zrc53aUjobb5L8T9TOedzfmhYYoupBXrbjOKIuhg3AHDLaa/MxSD0/gX4rIRD+SX
 hYVoOZDCYRUFeg==
X-ME-Sender: <xms:qxT5WJU5bFrU0Y0p1MGuPu60jIrAsCS9f0NulxyjNqSwKkopbwIWxg>
X-Sasl-enc: fxPGoG6rKCZ8MxcjsUpowta0/HwAjYE314aVRohaKZv/ 1492718762
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id D7C797E0EE;
 Thu, 20 Apr 2017 16:06:02 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: "Lu, Patrick" <patrick.lu@intel.com>
Cc: dev@dpdk.org
Date: Thu, 20 Apr 2017 22:06:01 +0200
Message-ID: <4740562.ruR7tigWuU@xps>
In-Reply-To: <EFC7DD9FAC418F4683FA895DBD8B35A30FC2F6A5@fmsmsx101.amr.corp.intel.com>
References: <EFC7DD9FAC418F4683FA895DBD8B35A30FC2F6A5@fmsmsx101.amr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] DPDK log system is not working
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 20:06:03 -0000

20/04/2017 20:35, Lu, Patrick:
> Hi,
> 
> I've recently rebased my DPDK code from v16.07 to v17.05-rc1 and learned
> rte_set_log_type() API is deprecated now, so I switched to
> rte_log_set_level() API.

It should be fixed with the recent patches.
Please check the master branch or 17.05-rc2 when it will be out.