All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yong Wang <yongwang@vmware.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	dev@dpdk.org, John McNamara <john.mcnamara@intel.com>
Subject: Re: [PATCH v9] net/kni: add KNI PMD
Date: Fri, 17 Feb 2017 23:37:56 +0100	[thread overview]
Message-ID: <4966535.E9V4giOa3W@xps13> (raw)
In-Reply-To: <BY2PR05MB235928A31499706A7BA10E09AF5D0@BY2PR05MB2359.namprd05.prod.outlook.com>

2017-02-17 17:52, Yong Wang:
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> > 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>

Sorry, it is not what I meant.
Your Reviewed-by is really strong to make confident the patch is good.
But Ferruh wanted to make sure more people wants this PMD.

  reply	other threads:[~2017-02-17 22:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 10:33 [PATCH] net/kni: add KNI PMD 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 ` [PATCH v2] " Ferruh Yigit
2016-10-10 13:19   ` [PATCH v3] " Ferruh Yigit
2016-11-03  1:24     ` Yong Wang
2016-11-04 12:21       ` Ferruh Yigit
2016-11-30 18:12     ` [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       ` [PATCH v5] " Ferruh Yigit
2017-01-30 19:05         ` Yong Wang
2017-01-30 19:43           ` Ferruh Yigit
2017-01-30 20:09         ` [PATCH v6] " Ferruh Yigit
2017-01-30 21:15           ` [PATCH v7] " Ferruh Yigit
2017-01-31 12:18             ` [PATCH v8] " Ferruh Yigit
2017-02-17 13:42               ` [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
2017-02-17 22:37                       ` Thomas Monjalon [this message]
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=4966535.E9V4giOa3W@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=yongwang@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.