[PATCHv5 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 2/7] tap: Renaming tap related APIs, data structures, macros · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 6/7] tap: tap as an independent module · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 7/7] ipvtap: IP-VLAN based tap driver · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 1/7] tap: Refactoring macvtap.c · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 5/7] tap: Extending tap device create/destroy APIs · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 4/7] tap: Abstract type of virtual interface from tap implementation · Sainath Grandhi <hidden> · 2017-02-08
[PATCHv5 3/7] tap: Tap character device creation/destroy API · Sainath Grandhi <hidden> · 2017-02-08
Re: [PATCHv5 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces · David Miller <davem@davemloft.net> · 2017-02-09
RE: [PATCHv5 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces · Grandhi, Sainath <hidden> · 2017-02-11

Re: [PATCHv5 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces

From: David Miller <davem@davemloft.net>
Date: 2017-02-09 22:07:44
Also in: lkml

From: Sainath Grandhi <redacted>
Date: Wed,  8 Feb 2017 13:37:09 -0800

Tap character devices can be implemented on other virtual interfaces like
ipvlan, similar to macvtap. Source code for tap functionality in macvtap
can be re-used for this purpose.

This patch series splits macvtap source into two modules, macvtap and tap.
This patch series also includes a patch for implementing tap character
device driver based on the IP-VLAN network interface, called ipvtap.

These patches are tested on x86 platform.

I get rejects on patch #7 when I try to apply this to net-next,
please respin.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help