netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: "David S. Miller" <davem@davemloft.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
	Sridhar Samudrala <sridhar.samudrala@intel.com>,
	linux-doc@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] docs: Fix failover build warnings
Date: Thu, 12 Jul 2018 07:42:48 +1000	[thread overview]
Message-ID: <20180711214250.19039-1-me@tobin.cc> (raw)

Hi Dave,

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.

thanks,
Tobin.


Tobin C. Harding (2):
  docs: networking: Add failover docs to index
  docs: networking: Fix failover build warnings

 Documentation/networking/index.rst        |   2 +
 Documentation/networking/net_failover.rst | 111 +++++++++++-----------
 2 files changed, 59 insertions(+), 54 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-07-11 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 21:42 Tobin C. Harding [this message]
2018-07-11 21:42 ` [PATCH net-next 1/2] docs: networking: Add failover docs to index Tobin C. Harding
2018-07-11 21:42 ` [PATCH net-next 2/2] docs: networking: Fix failover build warnings Tobin C. Harding
2018-07-13  9:04   ` FYI: " Markus Heiser
2018-07-16 18:28 ` [PATCH net-next 0/2] docs: " David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180711214250.19039-1-me@tobin.cc \
    --to=me@tobin.cc \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sridhar.samudrala@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).