linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: Tal Gilboa <talgi@mellanox.com>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH] Documentation: networking: add a chapter for the DIM library
Date: Thu, 10 Oct 2019 15:55:15 -0700	[thread overview]
Message-ID: <e9345b39-352e-cfc6-7359-9b681cb760e8@infradead.org> (raw)

From: Randy Dunlap <rdunlap@infradead.org>

Add a Documentation networking chapter for the DIM library.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Tal Gilboa <talgi@mellanox.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org
Cc: linux-rdma@vger.kernel.org
---
 Documentation/networking/index.rst   |    1 +
 Documentation/networking/lib-dim.rst |    6 ++++++
 2 files changed, 7 insertions(+)

--- linux-next-20191010.orig/Documentation/networking/index.rst
+++ linux-next-20191010/Documentation/networking/index.rst
@@ -33,6 +33,7 @@ Contents:
    scaling
    tls
    tls-offload
+   lib-dim
 
 .. only::  subproject and html
 
--- /dev/null
+++ linux-next-20191010/Documentation/networking/lib-dim.rst
@@ -0,0 +1,6 @@
+=====================================================
+Dynamic Interrupt Moderation (DIM) library interfaces
+=====================================================
+
+.. kernel-doc:: include/linux/dim.h
+    :internal:



             reply	other threads:[~2019-10-10 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 22:55 Randy Dunlap [this message]
2019-10-10 23:20 ` [PATCH] Documentation: networking: add a chapter for the DIM library Jakub Kicinski
2019-10-10 23:34   ` Randy Dunlap
2019-10-10 23:58     ` Jakub Kicinski
2019-10-11  0:01       ` Randy Dunlap
2019-10-11  0:33         ` Jakub Kicinski

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=e9345b39-352e-cfc6-7359-9b681cb760e8@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=talgi@mellanox.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).