From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Keith Wiles <keith.wiles@intel.com>
Cc: dev@dpdk.org, Vipin Varghese <vipin.varghese@intel.com>,
Ophir Munk <ophirmu@mellanox.com>
Subject: Re: [PATCH v5] net/tap: fix proto field for tun
Date: Tue, 22 May 2018 23:25:10 +0100 [thread overview]
Message-ID: <938464c9-46b9-0e73-8b46-e061e68f653a@intel.com> (raw)
In-Reply-To: <92b07784-511f-13bb-6803-0dfaa547e1e4@intel.com>
On 5/22/2018 11:19 PM, Ferruh Yigit wrote:
> On 5/22/2018 11:09 PM, Ferruh Yigit wrote:
>> From: Vipin Varghese <vipin.varghese@intel.com>
>>
>
> Proto filed is fixed for tap, so title should be:
> net/tap: fix proto field for tap
>
> Will fix while merging.
>
>> 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.
>>
>> Fixes: 204d026a3922 ("net/tap: support tun")
>> Cc: vipin.varghese@intel.com
>>
>> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-05-22 22:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 4:53 [PATCH] net/tap: perform proto field update for tun only Vipin Varghese
2018-05-14 22:27 ` Wiles, Keith
2018-05-15 9:08 ` Varghese, Vipin
2018-05-15 14:49 ` [PATCH v2] " Vipin Varghese
2018-05-15 12:31 ` Wiles, Keith
2018-05-15 22:28 ` Ophir Munk
2018-05-22 6:33 ` Varghese, Vipin
2018-05-22 11:05 ` Varghese, Vipin
2018-05-22 13:55 ` Wiles, Keith
2018-05-22 10:47 ` [PATCH v3] " Vipin Varghese
2018-05-22 13:53 ` Wiles, Keith
2018-05-23 4:33 ` Varghese, Vipin
2018-05-22 15:04 ` Ophir Munk
2018-05-23 4:37 ` Varghese, Vipin
2018-05-22 22:04 ` [PATCH v4] " Ferruh Yigit
2018-05-22 22:06 ` Ferruh Yigit
2018-05-22 22:09 ` [PATCH v5] net/tap: fix proto field for tun Ferruh Yigit
2018-05-22 22:19 ` Ferruh Yigit
2018-05-22 22:25 ` Ferruh Yigit [this message]
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=938464c9-46b9-0e73-8b46-e061e68f653a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=ophirmu@mellanox.com \
--cc=vipin.varghese@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 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.