From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/3] documentation related updates
Date: Mon, 18 May 2020 01:27:16 +0200 [thread overview]
Message-ID: <20200517232719.1789-1-luc.vanoostenryck@gmail.com> (raw)
Fix the doc generation with recent version of Sphinx,
fix the warnings in the doc generation and update the TODO.
Luc Van Oostenryck (3):
doc: do not use obsolete sphinx.ext.autodoc.AutodocReporter
doc: fix the warnings when building the doc
doc: remove done item from the TODO
Documentation/TODO.md | 12 +++++------
Documentation/nocast-vs-bitwise.md | 34 ++++++++++++++++--------------
Documentation/sphinx/cdoc.py | 10 ++++-----
3 files changed, 28 insertions(+), 28 deletions(-)
base-commit: b8fad4bcd02210912de8cbdefcd77e9ca743a575
--
2.26.2
next reply other threads:[~2020-05-17 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 23:27 Luc Van Oostenryck [this message]
2020-05-17 23:27 ` [PATCH 1/3] doc: do not use obsolete sphinx.ext.autodoc.AutodocReporter Luc Van Oostenryck
2020-05-17 23:27 ` [PATCH 2/3] doc: fix the warnings when building the doc Luc Van Oostenryck
2020-05-17 23:27 ` [PATCH 3/3] doc: remove done item from the TODO Luc Van Oostenryck
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=20200517232719.1789-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@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).