From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 0/6] net/sfc: implement dynamic logging Date: Fri, 26 Jan 2018 08:44:03 +0100 Message-ID: <5656127.1NENHmdK4C@xps> References: <1516899647-8541-1-git-send-email-arybchenko@solarflare.com> <56198984.NQf2azoMJa@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Olivier Matz To: Andrew Rybchenko Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 8022E1B366 for ; Fri, 26 Jan 2018 08:44:46 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 26/01/2018 06:59, Andrew Rybchenko: > On 01/26/2018 12:38 AM, Thomas Monjalon wrote: > > 25/01/2018 18:00, Andrew Rybchenko: > >> Unfortunately we're a bit late with dynamic logging implementation. > >> So, it can wait for 18.05 release cycle if required. > >> > >> The series adds EXPERIMENTAL EAL feature which removes dependency > >> on EAL arguments processing and log types registration. It stores > >> EAL loglevel arguments in the list and adds API function to register > >> a new log type and pick up its value from EAL arguments. > >> > >> For us it is important since we would like to be able to control > >> per-device log level, e.g. pmd.net.sfc.main.0000:01:00.0. > > Would it be possible to consider EAL patch for 18.05, > > and others for 18.02? > > Artefacts of the EAL patch are used in the subsequent patches, so > I think it does not make sense to redo subsequent patches without > the EAL one and, then, change it once again on the next release cycle. OK, no problem. We can wait 18.05.