From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 0375E2BF3 for ; Wed, 17 Jan 2018 14:23:23 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7C6BE20B7A; Wed, 17 Jan 2018 08:23:23 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 17 Jan 2018 08:23:23 -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=GR1khKSVo9DMWv4H9umRrUPYML TKrToVMUC1itMrM68=; b=aOY0xlXeARRhX6h1Mmolkqs3XHQ0vWJwZYWbC4Am5J RGNeb07aWwTSo/UMjUGJpCodQiQQ3Zv+L6Vksr/xVRziNOytysGR0nDlsXiI6x7Y cc51CoMEDTOQwPscCSA+TLBSuyWv2Gn2vbiDb3eOwhmtEqVUWaoE5UvR1kaSakYp E= 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=GR1khK SVo9DMWv4H9umRrUPYMLTKrToVMUC1itMrM68=; b=JBaNdXVM6M44dV1v4oR4Py Q0VJIrlAwWrxDQ1OkPYjKTJgFf8iwsEyqfk7F/TUvbAmF+pQ1kbPXnYHdlLNFK0F mBm/+o2/MFDbT2jdzknUxuypPeLYAG0fWVSDiCFZtatcB0OVqzgIzoEtigXGktZ8 kUNLWhBIOQWvpKyS7yVhPm6cJt9K0tF5+K0YWXbBffe8C8MDJMG7vTFIeyJOyoV/ EFzWhZWjGgubjBT7CcbybFtg72wPfag0pho7FKBZFK58RPcbLzZSm2mnMx+sVHRB 4WElkqrN++HHGkg7jdBZ+SIutEXP0DQ1Ewx4KFKv2hippb4sigPKTcZck2xP70EQ == 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 297062463E; Wed, 17 Jan 2018 08:23:23 -0500 (EST) From: Thomas Monjalon To: Pavan Nikhilesh Cc: dev@dpdk.org, Olivier MATZ , ferruh.yigit@intel.com Date: Wed, 17 Jan 2018 14:22:51 +0100 Message-ID: <10267387.yn3KPbUsfK@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: Wed, 17 Jan 2018 13:23:24 -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 Series applied, thanks