From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Vinod Koul" <vinod.koul@intel.com>,
"Thierry Reding" <treding@nvidia.com>,
"Sanyog Kale" <sanyog.r.kale@intel.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Sagar Dharia" <sdharia@codeaurora.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Kees Cook" <keescook@chromium.org>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 03/18] docs: */index.rst: Add newer documents to their respective index.rst
Date: Tue, 8 May 2018 05:07:30 +0200 [thread overview]
Message-ID: <20180508030730.GC1882@kroah.com> (raw)
In-Reply-To: <e6852448ac11e827f86dab1e183b82af6a320559.1525684985.git.mchehab+samsung@kernel.org>
On Mon, May 07, 2018 at 06:35:39AM -0300, Mauro Carvalho Chehab wrote:
> A number of new docs were added, but they're currently not on
> the index.rst from the session they're supposed to be, causing
> Sphinx warnings.
>
> Add them.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2018-05-08 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 9:35 [PATCH 00/18] Fix some build warnings/errors with Sphinx Mauro Carvalho Chehab
2018-05-07 9:35 ` [PATCH 03/18] docs: */index.rst: Add newer documents to their respective index.rst Mauro Carvalho Chehab
2018-05-08 3:07 ` Greg Kroah-Hartman [this message]
2018-05-08 15:59 ` Jonathan Corbet
2018-05-07 9:35 ` [PATCH 11/18] docs: crypto_engine.rst: Fix two parse warnings Mauro Carvalho Chehab
2018-05-08 16:13 ` [PATCH 00/18] Fix some build warnings/errors with Sphinx Jonathan Corbet
2018-05-08 17:36 ` Luis R. Rodriguez
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=20180508030730.GC1882@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=j.neuschaefer@gmx.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=keescook@chromium.org \
--cc=konstantin@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=sdharia@codeaurora.org \
--cc=treding@nvidia.com \
--cc=vinod.koul@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