From: David Miller <davem@davemloft.net>
To: me@tobin.cc
Cc: sridhar.samudrala@intel.com, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] docs: Fix failover build warnings
Date: Mon, 16 Jul 2018 11:28:13 -0700 (PDT) [thread overview]
Message-ID: <20180716.112813.1857756879663677102.davem@davemloft.net> (raw)
In-Reply-To: <20180711214250.19039-1-me@tobin.cc>
From: "Tobin C. Harding" <me@tobin.cc>
Date: Thu, 12 Jul 2018 07:42:48 +1000
> 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.
Series applied, thanks.
prev parent reply other threads:[~2018-07-16 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 21:42 [PATCH net-next 0/2] docs: Fix failover build warnings Tobin C. Harding
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 ` David Miller [this message]
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=20180716.112813.1857756879663677102.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--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).