Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 568a74d4 authored by David S. Miller's avatar David S. Miller
Browse files

Merge branch 'docs-Fix-failover-build-warnings'



Tobin C. Harding says:

====================
docs: Fix failover build warnings

This is my first patch set to net-next.  Please shout loud and clear if
I've botched anything.

Recently failover and net_failover modules were added to the mainline.
Documentation was included in rst format but they were not added to the
toctree in `networking/index.rst`.  Also building docs for net_failover
is currently emitting a few warnings.

Patch 1 adds failover and net_failover to the index toctree
Patch 2 fixes the build warnings for net_failover

I haven't been super active on netdev list so if there is some reason I
missed why these files are not in the index please do say so.

Has there been any discussion on preferred order for the toctree index
list?  I just added them to the bottom of the list.
====================

Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parents 35edb56e 28809849
Loading
Loading
Loading
Loading
+2 −0
Original line number Diff line number Diff line
@@ -15,6 +15,8 @@ Contents:
   kapi
   z8530book
   msg_zerocopy
   failover
   net_failover

.. only::  subproject

+57 −54
Original line number Diff line number Diff line
@@ -36,6 +36,7 @@ feature on the virtio-net interface and assign the same MAC address to both
virtio-net and VF interfaces.

Here is an example XML snippet that shows such configuration.
::

  <interface type='network'>
    <mac address='52:54:00:00:12:53'/>
@@ -56,6 +57,7 @@ Here is an example XML snippet that shows such configuration.

Booting a VM with the above configuration will result in the following 3
netdevs created in the VM.
::

  4: ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff
@@ -80,6 +82,7 @@ the paravirtual datapath when the VF is unplugged.

Here is a sample script that shows the steps to initiate live migration on
the source hypervisor.
::

  # cat vf_xml
  <interface type='hostdev' managed='yes'>