From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Ferruh Yigit <ferruh.yigit@intel.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: Fri, 16 Dec 2016 17:29:17 +0000 [thread overview]
Message-ID: <CAD+H990fau92xF1yKc=W72=pcNuw_v8fwTXdCVQ_eQPKod2zsQ@mail.gmail.com> (raw)
In-Reply-To: <6dcb23ec-4687-7397-bac0-1d72f3854f1e@intel.com>
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 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.
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.
On Fri, Dec 9, 2016 at 11:36 AM, Ferruh Yigit <ferruh.yigit@intel.com>
wrote:
> On 12/9/2016 10:00 AM, Alejandro Lucero wrote:
> > That's fine.
>
> Applied to dpdk-next-net/master, thanks.
>
> >
> > Thank you
> >
> > On Tue, Dec 6, 2016 at 4:01 PM, Ferruh Yigit <ferruh.yigit@intel.com
> > <mailto:ferruh.yigit@intel.com>> wrote:
> >
> > On 12/6/2016 2:51 PM, Alejandro Lucero wrote:
> > > Then I guess I should send another version of this patch.
> >
> > I can also update the patch while applying, if you agree with
> following
> > content (simply just all =N removed):
> >
> > [Features]
> > +SR-IOV = Y
> > +Link status = Y
> > +Link status event = Y
> > +Queue start/stop = Y
> > +MTU update = Y
> > +Jumbo frame = Y
> > +RSS hash = Y
> > +RSS key update = Y
> > +RSS reta update = Y
> > +Flow control = Y
> > +VLAN offload = Y
> > +L3 checksum offload = Y
> > +L4 checksum offload = Y
> > +Promiscuous mode = Y
> > +Basic stats = Y
> > +Stats per queue = Y
> > +Linux UIO = Y
> > +Linux VFIO = Y
> > +x86-64 = Y
> > +Usage doc = Y
> >
> >
> >
>
>
next prev parent reply other threads:[~2016-12-16 17:29 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 [this message]
2016-12-19 11:45 ` Ferruh Yigit
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='CAD+H990fau92xF1yKc=W72=pcNuw_v8fwTXdCVQ_eQPKod2zsQ@mail.gmail.com' \
--to=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).