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 8022E1B366 for ; Fri, 26 Jan 2018 08:44:46 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 327F920BB1; Fri, 26 Jan 2018 02:44:46 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 26 Jan 2018 02:44:46 -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=an14KLC2Wn2xqj+Rcu3hbuYtph fdxgNsjMYgOMS/nic=; b=WHR1V2mUNvLoX/g2pW8j2ZspLAOA1jSMyn0ygVeHtr EXj37DGURCDKjFwf2g24AkpS6b6MTzZoIt0TtGeVOAwD9nWBxPc7HMm96qg1Quaz nB29qmpmfkHWW19ei66R9EL6KEy6CrKVJQcmQvKfu6Yx0Md1e4A0eGZ426gFdZTr w= 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=an14KL C2Wn2xqj+Rcu3hbuYtphfdxgNsjMYgOMS/nic=; b=O19OVsVV75NUWtEMyPNGGm Sdy4V6lBrkfib0tUXUQAISPkt74qZyHaYhKCvijR+iHcoDFuU6+3nmRKfguYlKwh E+F5dZEZy0QxJHT6tC6LEJYdIOUAt6kVnfiEvlE9ElESzkfAnYs7m1AOPHTfJDBI fZsrVGAmn0KB2k26cadqANvpbKSKxr688xdLJagslPEnPDTu1vqBNm7mGSSMFWxM H/oYAY9QcaXk1J6UgKidNVAvf7WYsAL4PmzwUngZ2MUmpYISRR3m7O9yRzlHDf/R HoijHF6H6rtHbihVpP5+98KQlPgh00qWM5GnU7f2/xhYFToM38FTwLPaxORW6yZw == 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 DB2AB7E539; Fri, 26 Jan 2018 02:44:45 -0500 (EST) From: Thomas Monjalon To: Andrew Rybchenko Cc: dev@dpdk.org, Olivier Matz Date: Fri, 26 Jan 2018 08:44:03 +0100 Message-ID: <5656127.1NENHmdK4C@xps> In-Reply-To: References: <1516899647-8541-1-git-send-email-arybchenko@solarflare.com> <56198984.NQf2azoMJa@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/6] net/sfc: implement dynamic logging 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, 26 Jan 2018 07:44:46 -0000 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.