From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-f179.google.com (mail-ua0-f179.google.com [209.85.217.179]) by dpdk.org (Postfix) with ESMTP id 6C4892B88 for ; Mon, 19 Dec 2016 12:58:03 +0100 (CET) Received: by mail-ua0-f179.google.com with SMTP id 3so84001549uaz.3 for ; Mon, 19 Dec 2016 03:58:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Es5jvqOaLdTRxMq7OtjGh2glzQgg8gpJbYEyVO0Umq8=; b=Oem+0XXe+Ps08XVzTC65mcOXdFDiorIhd0KCk4C1YJ0WbgLjlAFEyJT1ZLkEZ03XLd jaYnU+/9QevetASQ7HVlRljopcrx9xNJMzd3sOUoFDzt2uYvTcfQAc0HRGwK+mGdHX6Q 3Q63OkdlUt/EXztG1vOOLyzKshv5sTWGIHTm6U+YmijrWUqvUdyYnV4d5uOpQ7Mxo28t p8szygEODyZddiyvjt2WxzCe9eAAKnO96ioBNMZeyUU+M8UtQHfZYwFerF3mZbnIiInz mF6ggUgTA6qTxxAi8cf2uaxd79xexfiM0c7nP1bZCT/SIagoYhhl/kjMn8/a129xeU/S tsSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Es5jvqOaLdTRxMq7OtjGh2glzQgg8gpJbYEyVO0Umq8=; b=R9iUa4cWhTcNKDynYSF4EPFFY7lRYaCUDwIb4BTgSfhhDcd7NS/mCVuVhSY2G1CfEy FJkX6xjb5bkZfLE6LppTs4u6+5fcuWsmtDrviDLONGIPmcFtNcpTur8AFhDfEtiF/hmd GQ4IoZN7QR1CqeP2PX4YZ36PaXgWM+uPs/w5F8Xiq4yWP4DFZot3VaCWTuyrHmN/UxtK QT8EuliM7q89jK8EhopXQYOZw7kKqFNsVrzxbQ6vjRfWNCkdNOU/jPRUzs7LLJ4NozuS d+hUuM8vnKXgMkagQQPi8tbKYP1lgrqya/cxkyXVsyFfRi/jwbJt8d8d+QgK4andxTuX GUyA== X-Gm-Message-State: AKaTC02V0uPbjwtgzMl3qBVtnkaS8FWxYTMsy9xWW6ioS+qLVq0PE+QTA84SYgzQwTtlmjlES6hcu8Cm7A3ZSXzw X-Received: by 10.176.71.134 with SMTP id v6mr10341769uac.174.1482148682974; Mon, 19 Dec 2016 03:58:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.46.3 with HTTP; Mon, 19 Dec 2016 03:58:02 -0800 (PST) In-Reply-To: <17e4540d-e11b-3854-1fe7-b4abfd95a40c@intel.com> References: <1480666653-35544-1-git-send-email-alejandro.lucero@netronome.com> <3133b0c5-672d-de7d-1690-815c7603e581@intel.com> <03ef24cd-9ef6-066c-ea9c-6ee10a480d70@intel.com> <6dcb23ec-4687-7397-bac0-1d72f3854f1e@intel.com> <17e4540d-e11b-3854-1fe7-b4abfd95a40c@intel.com> From: Alejandro Lucero Date: Mon, 19 Dec 2016 11:58:02 +0000 Message-ID: To: Ferruh Yigit Cc: "Mcnamara, John" , "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] nfp: add doc about supported features 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: Mon, 19 Dec 2016 11:58:04 -0000 On Mon, Dec 19, 2016 at 11:45 AM, Ferruh Yigit wrote: > On 12/16/2016 5:29 PM, Alejandro Lucero wrote: > > Hi, > > > > One question about this patch. I will send another patch soon which will > > require to modify the file created by this patch. So, should I use the > > dpdk-next for sending the new patch or the dpdk stable branch? > > I guess by "dpdk stable branch" you mean dpdk main repo, because we also > have stable sub-tree which is something else. > > Yes. That's what I meant. > > I > > understand that using the latter will imply some integration later, but > > I really do not know if I should facilitate things using dpdk-next in > > this case. > > If the patch is driver patch, please send to the next-net sub-tree, as a > PMD maintainer, I expect majority of your patches should target next-net. > > OK > If patch just touches the documentation of the driver, you can send it > to the main tree, but both next-net sub-tree and main tree are OK since > PMD documentation is not heavily modified, integration will be (mostly) > easy. > > Specific to the this document (feature.ini), since this is directly > correlated with PMD source code, to update this file, you need to update > the source code. And it is better to update this document in next-net as > part of the patchset that updates the PMD code. > > Fine. > > > > By the way, it is not just about this specific patch, because I have > > other almost ready which I want to push before the 16.02 deadline. > > Please push 17.02 patches as soon as possible, although there is > technically still some time for the integration deadline, practically > there is less because of holidays in between ... > > I'm working on this. I have been busy doing other more priority things but this is now top priority for me. Thanks > > > > > <...> >