From: Yong Wang <yongwang@vmware.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v9] net/kni: add KNI PMD
Date: Fri, 17 Feb 2017 17:52:24 +0000 [thread overview]
Message-ID: <BY2PR05MB235928A31499706A7BA10E09AF5D0@BY2PR05MB2359.namprd05.prod.outlook.com> (raw)
In-Reply-To: <86596f35-f483-e493-101e-f93969bd2f1b@intel.com>
> -----Original Message-----
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Friday, February 17, 2017 6:30 AM
> To: Thomas Monjalon <thomas.monjalon@6wind.com>
> Cc: dev@dpdk.org; John McNamara <john.mcnamara@intel.com>; Yong
> Wang <yongwang@vmware.com>
> Subject: Re: [PATCH v9] net/kni: add KNI PMD
>
> On 2/17/2017 1:47 PM, Thomas Monjalon wrote:
> > 2017-02-17 13:42, Ferruh Yigit:
> >> Add KNI PMD which wraps librte_kni for ease of use.
> >>
> >> KNI PMD can be used as any regular PMD to send / receive packets to the
> >> Linux networking stack.
> >>
> >> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> >> Reviewed-by: Yong Wang <yongwang@vmware.com>
> >> ---
I have the impression that Reviewed-by is good enough for a change to be accepted, which does not seem to be the case.
Acked-by: Yong Wang <yongwang@vmware.com>
> >>
> >> v9:
> >> * update for 17.05
> >
> > You keep updating this patch in the hope that someone would be
> interested :)
> >
> > Please let's make clear that I am OK to merge it
> > but you asked me to wait for someone supporting its inclusion.
>
> Right, it is good to mention that I explicitly asked to wait community
> response.
>
> I keep updating it because I believe this is something useful.
>
> Meanwhile adding this into repo means maintenance cost, so this should
> not be merged without any usecase or interest from community.
>
> Patch is waiting for an ACK or NAK from community.
>
> Thanks,
> ferruh
next prev parent reply other threads:[~2017-02-17 17:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 10:33 [dpdk-dev] [PATCH] " Ferruh Yigit
2016-09-08 7:44 ` Thomas Monjalon
2016-09-08 9:25 ` Bruce Richardson
2016-09-08 9:38 ` Thomas Monjalon
2016-09-08 18:11 ` Ferruh Yigit
2016-09-09 7:36 ` Thomas Monjalon
2016-09-16 11:29 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2016-10-10 13:19 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2016-11-03 1:24 ` Yong Wang
2016-11-04 12:21 ` Ferruh Yigit
2016-11-30 18:12 ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2016-12-12 21:59 ` Yong Wang
2016-12-14 15:59 ` Ferruh Yigit
2016-12-14 19:25 ` Yong Wang
2016-12-15 15:55 ` Ferruh Yigit
2016-12-19 17:52 ` Yong Wang
2017-01-30 16:57 ` [dpdk-dev] [PATCH v5] " Ferruh Yigit
2017-01-30 19:05 ` Yong Wang
2017-01-30 19:43 ` Ferruh Yigit
2017-01-30 20:09 ` [dpdk-dev] [PATCH v6] " Ferruh Yigit
2017-01-30 21:15 ` [dpdk-dev] [PATCH v7] " Ferruh Yigit
2017-01-31 12:18 ` [dpdk-dev] [PATCH v8] " Ferruh Yigit
2017-02-17 13:42 ` [dpdk-dev] [PATCH v9] " Ferruh Yigit
2017-02-17 13:47 ` Thomas Monjalon
2017-02-17 14:00 ` Eelco Chaudron
2017-02-17 14:29 ` Ferruh Yigit
2017-02-17 14:57 ` Bruce Richardson
2017-02-17 17:52 ` Yong Wang [this message]
2017-02-17 22:37 ` Thomas Monjalon
2017-02-20 12:54 ` Ferruh Yigit
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=BY2PR05MB235928A31499706A7BA10E09AF5D0@BY2PR05MB2359.namprd05.prod.outlook.com \
--to=yongwang@vmware.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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).