From: Jani Nikula <jani.nikula@intel.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: DocBook: Warning: The Sphinx 'sphinx_rtd_theme' HTML theme was not found. Make sure you have the theme installed to produce pretty HTML output. Falling back to the default theme.
Date: Mon, 01 Aug 2016 13:08:26 +0300 [thread overview]
Message-ID: <87bn1cvm1x.fsf@intel.com> (raw)
In-Reply-To: <201607281643.iTHo3Bqq%fengguang.wu@intel.com>
On Thu, 28 Jul 2016, kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 194dc870a5890e855ecffb30f3b80ba7c88f96d6
> commit: 22cba31bae9dc357622f09d22b82ca5a112b4fde Documentation/sphinx: add basic working Sphinx configuration and build
> date: 8 weeks ago
> reproduce: make htmldocs
>
> All warnings (new ones prefixed by >>):
>
>>> Warning: The Sphinx 'sphinx_rtd_theme' HTML theme was not found. Make sure you have the theme installed to produce pretty HTML output. Falling back to the default theme.
FWIW you can fix this by installing the sphinx_rtd_theme, but it's not
strictly necessary. The theme is packaged in several distros,
e.g. python-sphinx-rtd-theme in debian.
BR,
Jani.
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-08-01 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 8:01 DocBook: Warning: The Sphinx 'sphinx_rtd_theme' HTML theme was not found. Make sure you have the theme installed to produce pretty HTML output. Falling back to the default theme kbuild test robot
2016-08-01 10:08 ` Jani Nikula [this message]
2016-08-01 10:23 ` [kbuild-all] " Fengguang Wu
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=87bn1cvm1x.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@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