DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Wiles, Keith" <keith.wiles@intel.com>
Cc: DPDK <dev@dpdk.org>,
	"ophirmu@mellanox.com" <ophirmu@mellanox.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"olgas@mellanox.com" <olgas@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v4] net/tap: perform proto field update for tun only
Date: Wed, 23 May 2018 08:26:04 +0000	[thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D1F89CF@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <c3be7b30-b86b-bed9-e801-599901c729b0@intel.com>

Hi Ferruh,

I have checked the patch done. I am ok with the same.

Thanks
Vipin Varghese

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Wednesday, May 23, 2018 1:41 PM
> To: Wiles, Keith <keith.wiles@intel.com>; Varghese, Vipin
> <vipin.varghese@intel.com>
> Cc: DPDK <dev@dpdk.org>; ophirmu@mellanox.com; thomas@monjalon.net;
> olgas@mellanox.com
> Subject: Re: [PATCH v4] net/tap: perform proto field update for tun only
> 
> On 5/23/2018 5:48 AM, Wiles, Keith wrote:
> >
> >
> >> On May 22, 2018, at 11:44 PM, Varghese, Vipin <vipin.varghese@intel.com>
> wrote:
> >>
> >> The TX function is shared between TAP and TUN PMD. Checking TUN-TAP
> >> type field will ensure the TAP PMD will always have protocol field as
> >> 0.
> >>
> >> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> >> Suggested-by: Ferruh Yigit <ferruh.yigit@intel.com>
> >> ---
> >> Changes in V4:
> >> - convert comparision with MACRO - Keith Wiles
> >> - add LOG err for tun using set MAC - Ophir Munk
> >>
> >> Changes in V3:
> >> - remove type field from rx struct - Ophir Munk
> >> - add space for comment in struct - Ophir Munk
> >> - pass type field into eth_dev_tap_create - Ophir Munk
> >> - replace with enum value for type - Ophir Munk
> >> - return as 'not supported' for mac_set - Vipin Varghese
> >>
> >> Changes in V2:
> >> - updated in comment wording - Keith Wiles
> >> - remove debug print from tx code - Keith Wiles —
> >
> > Looks good to me.
> >
> > Acked-by: Keith Wiles<keith.wiles@intel.com>
> 
> I re-did a v5 for this patch yesterday and it has already been merged into rc5.
> https://dpdk.org/dev/patchwork/patch/40352/
> 
> @vipin, can you please check if the merged patch is good, and if is there any diff
> with what you have sent here?
> 
> Thanks,
> ferruh
> 
> >
> > Regards,
> > Keith
> >


  reply	other threads:[~2018-05-23  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  4:44 Vipin Varghese
2018-05-23  4:48 ` Wiles, Keith
2018-05-23  8:11   ` Ferruh Yigit
2018-05-23  8:26     ` Varghese, Vipin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-22 10:47 [dpdk-dev] [PATCH v3] " Vipin Varghese
2018-05-22 22:04 ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2018-05-22 22:06   ` 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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D1F89CF@BGSMSX101.gar.corp.intel.com \
    --to=vipin.varghese@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=keith.wiles@intel.com \
    --cc=olgas@mellanox.com \
    --cc=ophirmu@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).