<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/ipvlan/Makefile#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/net/ipvlan/Makefile</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>c675e06a - ipvlan: decouple l3s mode dependencies from other modes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/ipvlan/Makefile#c675e06a</link>
        <description>ipvlan: decouple l3s mode dependencies from other modesRight now ipvlan has a hard dependency on CONFIG_NETFILTER andotherwise it cannot be built. However, the only ipvlan operationmode that actually depends on netfilter is l3s, everything elseis independent of it. Break this hard dependency such that usersare able to use ipvlan l3 mode on systems where netfilter is notcompiled in.Therefore, this adds a hidden CONFIG_IPVLAN_L3S bool which isdefaulting to y when CONFIG_NETFILTER is set in order to retainexisting behavior for l3s. All l3s related code is refactoredinto ipvlan_l3s.c that is compiled in when enabled.Signed-off-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;Cc: Mahesh Bandewar &lt;maheshb@google.com&gt;Cc: Florian Westphal &lt;fw@strlen.de&gt;Cc: Martynas Pumputis &lt;m@lambda.lt&gt;Acked-by: Florian Westphal &lt;fw@strlen.de&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/ipvlan/Makefile</description>
        <pubDate>Fri, 08 Feb 2019 12:55:31 +0000</pubDate>
        <dc:creator>Daniel Borkmann &lt;daniel@iogearbox.net&gt;</dc:creator>
    </item>
<item>
        <title>235a9d89 - ipvtap: IP-VLAN based tap driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/ipvlan/Makefile#235a9d89</link>
        <description>ipvtap: IP-VLAN based tap driverThis patch adds a tap character device driver that is based on theIP-VLAN network interface, called ipvtap. An ipvtap device can be createdin the same way as an ipvlan device, using &apos;type ipvtap&apos;, and then accessedusing the tap user space interface.Signed-off-by: Sainath Grandhi &lt;sainath.grandhi@intel.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/ipvlan/Makefile</description>
        <pubDate>Sat, 11 Feb 2017 00:03:52 +0000</pubDate>
        <dc:creator>Sainath Grandhi &lt;sainath.grandhi@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>2ad7bf36 - ipvlan: Initial check-in of the IPVLAN driver.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/ipvlan/Makefile#2ad7bf36</link>
        <description>ipvlan: Initial check-in of the IPVLAN driver.This driver is very similar to the macvlan driver except that ituses L3 on the frame to determine the logical interface whilefunctioning as packet dispatcher. It inherits L2 of the masterdevice hence the packets on wire will have the same L2 for allthe packets originating from all virtual devices off of the samemaster device.This driver was developed keeping the namespace use-case inmind. Hence most of the examples given here take that as thebase setup where main-device belongs to the default-ns andvirtual devices are assigned to the additional namespaces.The device operates in two different modes and the differencein these two modes in primarily in the TX side.(a) L2 mode : In this mode, the device behaves as a L2 device.TX processing upto L2 happens on the stack of the virtual deviceassociated with (namespace). Packets are switched after thatinto the main device (default-ns) and queued for xmit.RX processing is simple and all multicast, broadcast (ifapplicable), and unicast belonging to the address(es) aredelivered to the virtual devices.(b) L3 mode : In this mode, the device behaves like a L3 device.TX processing upto L3 happens on the stack of the virtual deviceassociated with (namespace). Packets are switched to themain-device (default-ns) for the L2 processing. Hence the routingtable of the default-ns will be used in this mode.RX processins is somewhat similar to the L2 mode except that inthis mode only Unicast packets are delivered to the virtual devicewhile main-dev will handle all other packets.The devices can be added using the &quot;ip&quot; command from the iproute2package -	ip link add link &lt;master&gt; &lt;virtual&gt; type ipvlan mode [ l2 | l3 ]Signed-off-by: Mahesh Bandewar &lt;maheshb@google.com&gt;Cc: Eric Dumazet &lt;edumazet@google.com&gt;Cc: Maciej &#379;enczykowski &lt;maze@google.com&gt;Cc: Laurent Chavey &lt;chavey@google.com&gt;Cc: Tim Hockin &lt;thockin@google.com&gt;Cc: Brandon Philips &lt;brandon.philips@coreos.com&gt;Cc: Pavel Emelianov &lt;xemul@parallels.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/ipvlan/Makefile</description>
        <pubDate>Mon, 24 Nov 2014 07:07:46 +0000</pubDate>
        <dc:creator>Mahesh Bandewar &lt;maheshb@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
