From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id D25FC728E for ; Fri, 12 Jan 2018 16:47:16 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7D86E20D2A; Fri, 12 Jan 2018 10:47:16 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 12 Jan 2018 10:47:16 -0500 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; s=mesmtp; bh=8zPnBQ5+LHkgBDb/7eetbeN0Bx zKETgrSqEq/RyLBMg=; b=ZiwxJxAKeN7lbycSrO5YCNwHJA4Gz7Ab1JSEeDZevp FWgZGN4x+/yYIbWdFK4P2NFb8fZAG39odeH71dTpzSJGEtL8TAMgUCfPw3gUwQuN vaj7HEoEl3+0pUYiaDNmF+/miAvvAVv3rHgHgoMjr3FmCpVAJzhPXWMN0BsE72ec o= 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; s=fm1; bh=8zPnBQ 5+LHkgBDb/7eetbeN0BxzKETgrSqEq/RyLBMg=; b=m32TDrj93VynljIf1qCS7I W72zOKSGhqXsII4ynS8b5FZ5NJB1+iIDo0ERTTSkIvumMHAWIPvMqksOsjS8HGZ+ FvpzTMSDKRB7sUDi5bGQBfLfmzv2DrQkYi4nEF0stplqf1dtU2mcUPfMP9bJ2p6W cB1tUuGym/5kMOyGOR7X4FpZ6icC1oS1ntKK2chy7w9aLo1+AqoLfB8o7H0ta58z KUrQDi1gZ9p0BWDYa8U5Veuo0TEQyPWNUWGPf1L9dxruhlobJc/Omx5VsB7R7Khw SLeoeXrYL0CrmidLiZaqIgD18lmSOHSEEgmEMHK/f1kTuPi+CoBVM/fDeNCHZKsg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 2C57A24772; Fri, 12 Jan 2018 10:47:16 -0500 (EST) From: Thomas Monjalon To: Pavan Nikhilesh Cc: dev@dpdk.org, Olivier MATZ , ferruh.yigit@intel.com Date: Fri, 12 Jan 2018 16:46:47 +0100 Message-ID: <5726867.dobx3UARpb@xps> In-Reply-To: <20171212163620.pphb6ioehmze2oje@platinum> References: <20171122092806.17194-1-pbhagavatula@caviumnetworks.com> <20171209132358.24263-3-pbhagavatula@caviumnetworks.com> <20171212163620.pphb6ioehmze2oje@platinum> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 3/3] logs: remove log level config option X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 15:47:17 -0000 12/12/2017 17:36, Olivier MATZ: > On Sat, Dec 09, 2017 at 06:53:58PM +0530, Pavan Nikhilesh wrote: > > Remove RTE_LOG_LEVEL config option, use existing RTE_LOG_DP_LEVEL config > > option for controlling datapath log level. > > RTE_LOG_LEVEL is no longer needed as dynamic logging can be used to > > control global and module specific log levels. > > > > Signed-off-by: Pavan Nikhilesh > > Reviewed-by: Olivier Matz It breaks compilation of test/ directory. Please check git grep RTE_LOG_LEVEL