From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 44D3CA84E
 for <dev@dpdk.org>; Fri, 26 Jan 2018 14:18:44 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id BCB9F20BDF;
 Fri, 26 Jan 2018 08:18:43 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Fri, 26 Jan 2018 08:18:43 -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=II/g3LJG2MKqtKPbF4lY4h2CQt
 A6STYneJd27O3pTJw=; b=NRjyKp47aGa0JaXoiRjRcxzsSFqwZRS7fpfANizn1m
 TqKQu5LyB5r820HsOKQ0ehXHRd38oO551zlGSp04pkQLDQXdaCtSD+dj6u0CWVfW
 yeAkYVtrn2TmBIKyWikm0Wi9IBiOYqPPoXZkiIhpopmxavOSeeA7ZqxVj3gOOugk
 s=
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=II/g3L
 JG2MKqtKPbF4lY4h2CQtA6STYneJd27O3pTJw=; b=QP6ewEkkekXUQuM4HyVDuT
 UxbIovdhdWedbW1bslgzKWE2mH0t5epagfytr/dhuhNMGgFHSAu8M6dJD8ENOzy6
 GkU77O++eXOwfLH/ESFQ68+bDrE1iPSCg70qgTudXKrpZiAV6SsPo1Oea6YWCcMR
 EuIVQpkr1c6tj/XanRKjZ1FQy4ZGMyPZENHhUokydUOGmFrdNs25I7gWjuB/JdaX
 bpasbKn4ZXr7jR6kcgDJcyKeX9NwrMMNJuC5qlNP3umBIudiYVV3l8GLogg6DI0y
 NC/FCgqH225Z5CEEz033p1T6g1Qw9GwRxjY0m6El5YzBharYrmMAz1UEii7KiBAA
 ==
X-ME-Sender: <xms:syprWpxgVOttUQWz_PUJOGDcxEcgz0Cg82-664eqtFr8AIQdfZhqiA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 6A9707E12E;
 Fri, 26 Jan 2018 08:18:43 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, "Richardson, Bruce" <bruce.richardson@intel.com>, "Varghese,
 Vipin" <vipin.varghese@intel.com>
Date: Fri, 26 Jan 2018 14:18:01 +0100
Message-ID: <1539962.QZfzRtm2f4@xps>
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA650FFF798@IRSMSX102.ger.corp.intel.com>
References: <1514731568-3979-1-git-send-email-vipin.varghese@intel.com>
 <1706116.QiZev3mjbx@xps>
 <E923DB57A917B54B9182A2E928D00FA650FFF798@IRSMSX102.ger.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v2] service: fix memory leak by
	rte_service_init
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 13:18:44 -0000

26/01/2018 11:10, Van Haaren, Harry:
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Your patches have been set to "Not Applicable" in patchwork.
> > What happened?
> 
> There was some confusion in my review-comments, and Vipin and I discussed
> the best was to rework - I suggested marking the current patches as Not Applicable.
> 
> Is there a better state to put the patches in Patchwork if we don't want commiters to look at them?
> Or would an email to the thread stating V+1 in progress be better?

Yes, an email is always good to notify about the status.
In patchwork, you can use the state "Changes requested".
"Not Applicable" is used for patches which were never intended
to be applicable.

> A new version will hit the ML soon.