From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] service: fix memory leak by rte_service_init Date: Fri, 26 Jan 2018 14:18:01 +0100 Message-ID: <1539962.QZfzRtm2f4@xps> References: <1514731568-3979-1-git-send-email-vipin.varghese@intel.com> <1706116.QiZev3mjbx@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, "Richardson, Bruce" , "Varghese, Vipin" To: "Van Haaren, Harry" Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 44D3CA84E for ; Fri, 26 Jan 2018 14:18:44 +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 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.