From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: deadline notice Date: Thu, 11 Jun 2015 13:39:54 +0200 Message-ID: <1910067.s2MvseVWWd@xps13> References: <2520130.3p9lvqUWmZ@xps13> <159365803.3qspsHhf2U@xps13> <8CEF83825BEC744B83065625E567D7C204A2E551@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Iremonger, Bernard" Return-path: Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id 9187E5A9B for ; Thu, 11 Jun 2015 13:40:51 +0200 (CEST) Received: by wgbgq6 with SMTP id gq6so3648397wgb.3 for ; Thu, 11 Jun 2015 04:40:51 -0700 (PDT) In-Reply-To: <8CEF83825BEC744B83065625E567D7C204A2E551@IRSMSX108.ger.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-06-11 10:04, Iremonger, Bernard: > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > Note: [RFC] should be preferred for incomplete patches or trials. > > Should RFC PATCH be retained for v2 and subsequent patches or should RFC be dropped? If you target an integration of your patch, the RFC keyword must be dropped.