datapath: Use FIELD_SIZEOF() in dp_init().

[sliver-openvswitch.git] / FAQ

diff --git a/FAQ b/FAQ
index 190bf18..a5c0cb9 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -133,10 +133,10 @@ Q: What Linux kernel versions does each Open vSwitch release work with?
 A: The following table lists the Linux kernel versions against which the
    given versions of the Open vSwitch kernel module will successfully
    build.  The Linux kernel versions are upstream kernel versions, so
-   modified Linux kernels modified from the upstream sources may not
-   build in some cases even if they are based on a supported version.
-   This is most notably true of Red Hat Enterprise Linux (RHEL) kernels,
-   which are extensively modified from upstream.
+   Linux kernels modified from the upstream sources may not build in
+   some cases even if they are based on a supported version.  This is
+   most notably true of Red Hat Enterprise Linux (RHEL) kernels, which
+   are extensively modified from upstream.
 
    Open vSwitch   Linux kernel
    ------------   -------------
@@ -160,15 +160,6 @@ Q: What features are not available in the Open vSwitch kernel datapath
 A: The kernel module in upstream Linux 3.3 and later does not include
    the following features:
 
-       - Bridge compatibility, that is, support for the ovs-brcompatd
-         daemon that (if you enable it) lets "brctl" and other Linux
-         bridge tools transparently work with Open vSwitch instead.
-
-         We do not expect bridge compatibility to ever be available in
-         upstream Linux.  If you need bridge compatibility, use the
-         kernel module from the Open vSwitch distribution instead of the
-         upstream Linux kernel module.
-
        - Tunnel virtual ports, that is, interfaces with type "gre",
          "ipsec_gre", "capwap".  It is possible to create tunnels in
          Linux and attach them to Open vSwitch as system devices.