From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by dpdk.org (Postfix) with ESMTP id A2D4E593E for ; Thu, 16 Oct 2014 18:38:33 +0200 (CEST) Received: by mail-wi0-f182.google.com with SMTP id n3so5272228wiv.15 for ; Thu, 16 Oct 2014 09:46:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=I/e/560SZ1Ju9BeKNAWEFUiJXtTsC6sg3UNCRmhKAv0=; b=fW5KcyZxWwa88fcAEZcc1fsuw5IBsfqM/QEZ7YWStmx7jdKpYnReQaR3983tNeR39t JgJi4PgGyRz5a8luiO2fc/Y7YGbJqNlfNSzkRYcrimqB0RvwBYAz/f/lJRZcHeUYh5Zf 0mJlCuQXfZTY0HB3509MMkXpHck7Sp8R6CCmJ3kjqdXhyMGM3iSO92S3KVnh5eJq2d4c ZYicurFFP/MprBJysf1ncpMOLByjsR2jYtddTUF0swRt7Zc+k3InwRXww+cWFNYcmDOm 7gU4PkJt1UjkYcq0L/4IqcawAoiTwbPoMHBKN42pgi+4BLrQjEbfEkkVSs33b5C7gQyE xM3Q== X-Gm-Message-State: ALoCoQnT+sJClh5R9BnYiVH38b3GdRxlW7ULx/2J4JeRbiWTk8InqM5YSFZVpvHlIhetutuAPvDz X-Received: by 10.194.119.164 with SMTP id kv4mr3781546wjb.86.1413477987737; Thu, 16 Oct 2014 09:46:27 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id y5sm2602328wix.10.2014.10.16.09.46.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Oct 2014 09:46:26 -0700 (PDT) From: Thomas Monjalon To: Cristian Dumitrescu Date: Thu, 16 Oct 2014 18:46:10 +0200 Message-ID: <10629744.mhUtJ8hJ7T@xps13> Organization: 6WIND User-Agent: KMail/4.14.1 (Linux/3.16.4-1-ARCH; KDE/4.14.1; x86_64; ; ) In-Reply-To: <1401905319-8882-21-git-send-email-cristian.dumitrescu@intel.com> References: <1401905319-8882-1-git-send-email-cristian.dumitrescu@intel.com> <1401905319-8882-21-git-send-email-cristian.dumitrescu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [v2 20/23] librte_cfgfile: interpret config files X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 16:38:33 -0000 Hi Cristian, 2014-06-04 19:08, Cristian Dumitrescu: > This library provides a tool to interpret config files that have standard > structure. > > It is used by the Packet Framework examples/ip_pipeline sample application. > > It originates from examples/qos_sched sample application and now it makes > this code available as a library for other sample applications to use. > The code duplication with qos_sched sample app to be addressed later. 4 months ago, you said that this duplication will be adressed later. Neither you nor anyone at Intel submitted a patch to clean up that. I just want to be sure that "later" doesn't mean "never" because I'm accepting another "later" word for cleaning old filtering API. Maybe you just forgot it so please prove me that I'm right to accept "later" clean-up, in general. Thanks -- Thomas