From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] nfp: add doc about supported features
Date: Mon, 19 Dec 2016 11:45:30 +0000 [thread overview]
Message-ID: <17e4540d-e11b-3854-1fe7-b4abfd95a40c@intel.com> (raw)
In-Reply-To: <CAD+H990fau92xF1yKc=W72=pcNuw_v8fwTXdCVQ_eQPKod2zsQ@mail.gmail.com>
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.
> 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.
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.
>
> 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 ...
>
>
<...>
next prev parent reply other threads:[~2016-12-19 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 8:17 Alejandro Lucero
2016-12-02 10:56 ` Mcnamara, John
2016-12-06 12:08 ` Ferruh Yigit
2016-12-06 12:46 ` Mcnamara, John
2016-12-06 14:51 ` Alejandro Lucero
2016-12-06 16:01 ` Ferruh Yigit
2016-12-09 10:00 ` Alejandro Lucero
2016-12-09 11:36 ` Ferruh Yigit
2016-12-16 17:29 ` Alejandro Lucero
2016-12-19 11:45 ` Ferruh Yigit [this message]
2016-12-19 11:58 ` Alejandro Lucero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17e4540d-e11b-3854-1fe7-b4abfd95a40c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).