From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 2/2] eal: fix dynamic logs failing to print Date: Thu, 16 Nov 2017 11:48:14 -0800 Message-ID: <81bb5aae-527d-5b1a-5609-985256682d39@intel.com> References: <20171116103144.4197-1-pbhagavatula@caviumnetworks.com> <20171116103144.4197-2-pbhagavatula@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Pavan Nikhilesh , olivier.matz@6wind.com, thomas@monjalon.net Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 01F5D1B21A for ; Thu, 16 Nov 2017 20:48:16 +0100 (CET) In-Reply-To: <20171116103144.4197-2-pbhagavatula@caviumnetworks.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 11/16/2017 2:31 AM, Pavan Nikhilesh wrote: > Dynamic logs fail to print if the global log level is less than dynamic > loglevel. Example if the global log level is set to INFO and dynamic log > level for a specific module is set to DEBUG then the log fails to print. What is the purpose of the global log level value? > Check modules log level before checking the global log level. > > Fixes: c1b5fa94a46f ("eal: support dynamic log types") > > Signed-off-by: Pavan Nikhilesh <...>