From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Trivial" <qemu-trivial@nongnu.org>
Subject: Re: [PATCH] docs/sphinx/kerneldoc.py: Honour --enable-werror
Date: Thu, 16 Mar 2023 13:08:14 +0100 [thread overview]
Message-ID: <d755da2b-edd9-8337-1975-548c961fbe88@redhat.com> (raw)
In-Reply-To: <20230314114431.1096972-1-peter.maydell@linaro.org>
On 14/03/2023 12.44, Peter Maydell wrote:
> Currently, the kerneldoc Sphinx plugin doesn't honour the
> --enable-werror configure option, so its warnings are never fatal.
> This is because although we do pass sphinx-build the -W switch, the
> warnings from kerneldoc are produced by the scripts/kernel-doc script
> directly and don't go through Sphinx's "emit a warning" function.
>
> When --enable-werror is in effect, pass sphinx-build an extra
> argument -Dkerneldoc_werror=1. The kerneldoc plugin can then use
> this to determine whether it should be passing the kernel-doc script
> -Werror.
>
> We do this because there is no documented mechanism for
> a Sphinx plugin to determine whether sphinx-build was
> passed -W or not; if one is provided then we can switch to
> that at a later date:
> https://github.com/sphinx-doc/sphinx/issues/11239
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> NB: we need to land the fix for the current outstanding
> warning before this one can go in...
> https://lore.kernel.org/qemu-devel/20230310103123.2118519-11-alex.bennee@linaro.org/
> ---
> docs/meson.build | 2 +-
> docs/sphinx/kerneldoc.py | 5 +++++
> 2 files changed, 6 insertions(+), 1 deletion(-)
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-03-16 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 11:44 [PATCH] docs/sphinx/kerneldoc.py: Honour --enable-werror Peter Maydell
2023-03-16 12:08 ` Thomas Huth [this message]
2023-03-16 13:40 ` Laurent Vivier
2023-03-16 13:42 ` Peter Maydell
2023-03-16 15:16 ` Laurent Vivier
2023-03-16 15:23 ` Peter Maydell
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=d755da2b-edd9-8337-1975-548c961fbe88@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).