netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: 20190930113754.5902855e@cakuba.netronome.com, adam.zerella@gmail.com
Cc: jakub.kicinski@netronome.com, netdev@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: networking: Add title caret and missing doc
Date: Tue, 01 Oct 2019 09:20:00 -0700 (PDT)	[thread overview]
Message-ID: <20191001.092000.1273747856120657963.davem@davemloft.net> (raw)
In-Reply-To: <20191001111658.GA10429@gmail.com>

From: Adam Zerella <adam.zerella@gmail.com>
Date: Tue, 1 Oct 2019 21:16:58 +1000

> Resolving a couple of Sphinx documentation warnings
> that are generated in the networking section.
> 
> - WARNING: document isn't included in any toctree
> - WARNING: Title underline too short.
> 
> Signed-off-by: Adam Zerella <adam.zerella@gmail.com>

Applied.

      reply	other threads:[~2019-10-01 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 11:16 [PATCH v2] docs: networking: Add title caret and missing doc Adam Zerella
2019-10-01 16:20 ` 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=20191001.092000.1273747856120657963.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=20190930113754.5902855e@cakuba.netronome.com \
    --cc=adam.zerella@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).