linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Otto Sabart <ottosabart@seberm.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 3/3] doc: networking: add scaling doc into index file
Date: Wed, 9 Jan 2019 20:57:50 +0100	[thread overview]
Message-ID: <f34b41f5660f9c1d15ce44011929ea28d7f0cbe9.1547063330.git.ottosabart@seberm.com> (raw)
In-Reply-To: <cover.1547063330.git.ottosabart@seberm.com>

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

Add reference to scaling document into main table of contents in network
documentation.

Signed-off-by: Otto Sabart <ottosabart@seberm.com>
---
 Documentation/networking/index.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst
index 6a47629ef8ed..47552ea410fe 100644
--- a/Documentation/networking/index.rst
+++ b/Documentation/networking/index.rst
@@ -32,6 +32,7 @@ Contents:
    alias
    bridge
    snmp_counter
+   scaling
 
 .. only::  subproject
 
-- 
2.17.2


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-01-09 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 19:57 [PATCH 0/3] doc: networking: integrate scaling document into doc tree Otto Sabart
2019-01-09 19:57 ` [PATCH 1/3] doc: networking: prepare scaling document for conversion into RST Otto Sabart
2019-01-16 22:03   ` Jonathan Corbet
2019-01-09 19:57 ` [PATCH 2/3] doc: networking: convert scaling doc " Otto Sabart
2019-01-09 19:57 ` Otto Sabart [this message]
2019-01-16  4:35 ` [PATCH 0/3] doc: networking: integrate scaling document into doc tree 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=f34b41f5660f9c1d15ce44011929ea28d7f0cbe9.1547063330.git.ottosabart@seberm.com \
    --to=ottosabart@seberm.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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).