From: Jonathan Corbet <corbet@lwn.net>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Willem de Bruijn <willemb@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: add index entry for networking/msg_zerocopy
Date: Tue, 9 Jan 2018 10:58:23 -0700 [thread overview]
Message-ID: <20180109105823.0b2abdd3@lwn.net> (raw)
In-Reply-To: <1515202237-17214-1-git-send-email-me@tobin.cc>
On Sat, 6 Jan 2018 12:30:37 +1100
"Tobin C. Harding" <me@tobin.cc> wrote:
> Currently msg_zerocopy is not included in any toctree. Sphinx emits a
> build warning to this effect. The other three rst files in
> Documentation/networking are all indexed. We can add msg_zerocopy to the
> toctree to enable navigation of the document via HTML kernel docs.
>
> Add msg_zerocopy to the networking/ toctree.
We had a bit of a race condition here, and this fix was sent in by two
people. Dave Miller took the other one, so I'll drop this one. Sorry
about that - thanks for the fix!
jon
next prev parent reply other threads:[~2018-01-09 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 1:30 Tobin C. Harding
2018-01-09 17:58 ` Jonathan Corbet [this message]
2018-01-09 20:23 ` Tobin C. Harding
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=20180109105823.0b2abdd3@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=willemb@google.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
Powered by JetHome