<?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>c4ab7b56 - openvswitch: add trace points</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#c4ab7b56</link>
        <description>openvswitch: add trace pointsThis makes openvswitch module use the event tracing frameworkto log the upcall interface and action execution pipeline.  Whenusing openvswitch as the packet forwarding engine, some types ofdebugging are made possible simply by using the ovs-vswitchd&apos;sofproto/trace command.  However, such a command has somelimitations:  1. When trying to trace packets that go through the CT action,     the state of the packet can&apos;t be determined, and probably     would be potentially wrong.  2. Deducing problem packets can sometimes be difficult as well     even if many of the flows are known  3. It&apos;s possible to use the openvswitch module even without     the ovs-vswitchd (although, not common use).Introduce the event tracing points here to make it possible forworking through these problems in kernel space.  The style iscopied from the mac80211 driver-trace / trace code forconsistency - this creates some checkpatch splats, but theofficial &apos;guide&apos; for adding tracepoints, as well as the existingexamples all add the same splats so it seems acceptable.Signed-off-by: Aaron Conole &lt;aconole@redhat.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Tue, 22 Jun 2021 14:02:33 +0000</pubDate>
        <dc:creator>Aaron Conole &lt;aconole@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>96fbc13d - openvswitch: Add meter infrastructure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#96fbc13d</link>
        <description>openvswitch: Add meter infrastructureOVS kernel datapath so far does not support Openflow meter action.This is the first stab at adding kernel datapath meter support.This implementation supports only drop band type.Signed-off-by: Andy Zhou &lt;azhou@ovn.org&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Fri, 10 Nov 2017 20:09:42 +0000</pubDate>
        <dc:creator>Andy Zhou &lt;azhou@ovn.org&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-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/net/openvswitch/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>f88f69dd - openvswitch: Remove conntrack Kconfig option.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#f88f69dd</link>
        <description>openvswitch: Remove conntrack Kconfig option.There&apos;s no particular desire to have conntrack action support in OpenvSwitch as an independently configurable bit, rather just to ensurethere is not a hard dependency. This exposed option doesn&apos;t accuratelyreflect the conntrack dependency when enabled, so simplify this byremoving the option. Compile the support if NF_CONNTRACK is enabled.Fixes: 7f8a436eaa2c (&quot;openvswitch: Add conntrack action&quot;)Signed-off-by: Joe Stringer &lt;joestringer@nicira.com&gt;Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Fri, 04 Sep 2015 20:07:40 +0000</pubDate>
        <dc:creator>Joe Stringer &lt;joestringer@nicira.com&gt;</dc:creator>
    </item>
<item>
        <title>7f8a436e - openvswitch: Add conntrack action</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#7f8a436e</link>
        <description>openvswitch: Add conntrack actionExpose the kernel connection tracker via OVS. Userspace components canmake use of the CT action to populate the connection state (ct_state)field for a flow. This state can be subsequently matched.Exposed connection states are OVS_CS_F_*:- NEW (0x01) - Beginning of a new connection.- ESTABLISHED (0x02) - Part of an existing connection.- RELATED (0x04) - Related to an established connection.- INVALID (0x20) - Could not track the connection for this packet.- REPLY_DIR (0x40) - This packet is in the reply direction for the flow.- TRACKED (0x80) - This packet has been sent through conntrack.When the CT action is executed by itself, it will send the packetthrough the connection tracker and populate the ct_state field with oneor more of the connection state flags above. The CT action will alwaysset the TRACKED bit.When the COMMIT flag is passed to the conntrack action, this specifiesthat information about the connection should be stored. This allowssubsequent packets for the same (or related) connections to becorrelated with this connection. Sending subsequent packets for theconnection through conntrack allows the connection tracker to considerthe packets as ESTABLISHED, RELATED, and/or REPLY_DIR.The CT action may optionally take a zone to track the flow within. Thisallows connections with the same 5-tuple to be kept logically separatefrom connections in other zones. If the zone is specified, then the&quot;ct_zone&quot; match field will be subsequently populated with the zone id.IP fragments are handled by transparently assembling them as part of theCT action. The maximum received unit (MRU) size is tracked so thatrefragmentation can occur during output.IP frag handling contributed by Andy Zhou.Based on original design by Justin Pettit.Signed-off-by: Joe Stringer &lt;joestringer@nicira.com&gt;Signed-off-by: Justin Pettit &lt;jpettit@nicira.com&gt;Signed-off-by: Andy Zhou &lt;azhou@nicira.com&gt;Acked-by: Thomas Graf &lt;tgraf@suug.ch&gt;Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Wed, 26 Aug 2015 18:31:48 +0000</pubDate>
        <dc:creator>Joe Stringer &lt;joestringer@nicira.com&gt;</dc:creator>
    </item>
<item>
        <title>dcc38c03 - openvswitch: Re-add CONFIG_OPENVSWITCH_VXLAN</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#dcc38c03</link>
        <description>openvswitch: Re-add CONFIG_OPENVSWITCH_VXLANThis readds the config option CONFIG_OPENVSWITCH_VXLAN to avoid ahard dependency of OVS on VXLAN. It moves the VXLAN config compatcode to vport-vxlan.c and allows compliation as a module.Fixes: 614732eaa12d (&quot;openvswitch: Use regular VXLAN net_device device&quot;)Fixes: 2661371ace96 (&quot;openvswitch: fix compilation when vxlan is a module&quot;)Cc: Pravin B Shelar &lt;pshelar@nicira.com&gt;Cc: Nicolas Dichtel &lt;nicolas.dichtel@6wind.com&gt;Signed-off-by: Thomas Graf &lt;tgraf@suug.ch&gt;Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Wed, 29 Jul 2015 11:52:06 +0000</pubDate>
        <dc:creator>Thomas Graf &lt;tgraf@suug.ch&gt;</dc:creator>
    </item>
<item>
        <title>614732ea - openvswitch: Use regular VXLAN net_device device</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#614732ea</link>
        <description>openvswitch: Use regular VXLAN net_device deviceThis gets rid of all OVS specific VXLAN code in the receive andtransmit path by using a VXLAN net_device to represent the vport.Only a small shim layer remains which takes care of handling theVXLAN specific OVS Netlink configuration.Unexports vxlan_sock_add(), vxlan_sock_release(), vxlan_xmit_skb()since they are no longer needed.Signed-off-by: Thomas Graf &lt;tgraf@suug.ch&gt;Signed-off-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Tue, 21 Jul 2015 08:44:06 +0000</pubDate>
        <dc:creator>Thomas Graf &lt;tgraf@suug.ch&gt;</dc:creator>
    </item>
<item>
        <title>62b9c8d0 - ovs: Turn vports with dependencies into separate modules</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#62b9c8d0</link>
        <description>ovs: Turn vports with dependencies into separate modulesThe internal and netdev vport remain part of openvswitch.ko. Encapvports including vxlan, gre, and geneve can be built as separatemodules and are loaded on demand. Modules can be unloaded after use.Datapath ports keep a reference to the vport module during theirlifetime.Allows to remove the error prone maintenance of the global listvport_ops_list.Signed-off-by: Thomas Graf &lt;tgraf@suug.ch&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Wed, 22 Oct 2014 15:29:06 +0000</pubDate>
        <dc:creator>Thomas Graf &lt;tgraf@suug.ch&gt;</dc:creator>
    </item>
<item>
        <title>f5796684 - openvswitch: Add support for Geneve tunneling.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#f5796684</link>
        <description>openvswitch: Add support for Geneve tunneling.The Openvswitch implementation is completely agnostic to the optionsthat are in use and can handle newly defined options withoutfurther work. It does this by simply matching on a byte arrayof options and allowing userspace to setup flows on this array.Signed-off-by: Jesse Gross &lt;jesse@nicira.com&gt;Singed-off-by: Ansis Atteka &lt;aatteka@nicira.com&gt;Signed-off-by: Andy Zhou &lt;azhou@nicira.com&gt;Acked-by: Thomas Graf &lt;tgraf@noironetworks.com&gt;Acked-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Fri, 03 Oct 2014 22:35:33 +0000</pubDate>
        <dc:creator>Jesse Gross &lt;jesse@nicira.com&gt;</dc:creator>
    </item>
<item>
        <title>e6445719 - openvswitch: Restructure datapath.c and flow.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#e6445719</link>
        <description>openvswitch: Restructure datapath.c and flow.cOver the time datapath.c and flow.c has became pretty large files.Following patch restructures functionality of component into threedifferent components:flow.c: contains flow extract.flow_netlink.c: netlink flow api.flow_table.c: flow table api.This patch restructures code without changing logic.Signed-off-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: Jesse Gross &lt;jesse@nicira.com&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Fri, 04 Oct 2013 01:16:47 +0000</pubDate>
        <dc:creator>Pravin B Shelar &lt;pshelar@nicira.com&gt;</dc:creator>
    </item>
<item>
        <title>3fa34de6 - openvswitch: check CONFIG_OPENVSWITCH_GRE in makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#3fa34de6</link>
        <description>openvswitch: check CONFIG_OPENVSWITCH_GRE in makefileCc: Jesse Gross &lt;jesse@nicira.com&gt;Cc: Pravin B Shelar &lt;pshelar@nicira.com&gt;Signed-off-by: Cong Wang &lt;amwang@redhat.com&gt;Signed-off-by: Jesse Gross &lt;jesse@nicira.com&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Tue, 20 Aug 2013 17:48:15 +0000</pubDate>
        <dc:creator>Cong Wang &lt;amwang@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>58264848 - openvswitch: Add vxlan tunneling support.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#58264848</link>
        <description>openvswitch: Add vxlan tunneling support.Following patch adds vxlan vport type for openvswitch usingvxlan api. So now there is vxlan dependency for openvswitch.CC: Jesse Gross &lt;jesse@nicira.com&gt;Signed-off-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Acked-by: Jesse Gross &lt;jesse@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Mon, 19 Aug 2013 18:23:34 +0000</pubDate>
        <dc:creator>Pravin B Shelar &lt;pshelar@nicira.com&gt;</dc:creator>
    </item>
<item>
        <title>aa310701 - openvswitch: Add gre tunnel support.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#aa310701</link>
        <description>openvswitch: Add gre tunnel support.Add gre vport implementation.  Most of gre protocol processingis pushed to gre module. It make use of gre demultiplexertherefore it can co-exist with linux device based gre tunnels.Signed-off-by: Pravin B Shelar &lt;pshelar@nicira.com&gt;Acked-by: Jesse Gross &lt;jesse@nicira.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Tue, 18 Jun 2013 00:50:33 +0000</pubDate>
        <dc:creator>Pravin B Shelar &lt;pshelar@nicira.com&gt;</dc:creator>
    </item>
<item>
        <title>ccb1352e - net: Add Open vSwitch kernel components.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/net/openvswitch/Makefile#ccb1352e</link>
        <description>net: Add Open vSwitch kernel components.Open vSwitch is a multilayer Ethernet switch targeted at virtualizedenvironments.  In addition to supporting a variety of featuresexpected in a traditional hardware switch, it enables fine-grainedprogrammatic extension and flow-based control of the network.This control is useful in a wide variety of applications but isparticularly important in multi-server virtualization deployments,which are often characterized by highly dynamic endpoints and the needto maintain logical abstractions for multiple tenants.The Open vSwitch datapath provides an in-kernel fast path for packetforwarding.  It is complemented by a userspace daemon, ovs-vswitchd,which is able to accept configuration from a variety of sources andtranslate it into packet processing rules.See http://openvswitch.org for more information and userspaceutilities.Signed-off-by: Jesse Gross &lt;jesse@nicira.com&gt;

            List of files:
            /linux-6.15/net/openvswitch/Makefile</description>
        <pubDate>Wed, 26 Oct 2011 02:26:31 +0000</pubDate>
        <dc:creator>Jesse Gross &lt;jesse@nicira.com&gt;</dc:creator>
    </item>
</channel>
</rss>
