From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [PATCH 0/2] docs: Fix building with Sphinx 3.2
Date: Sat, 31 Oct 2020 15:58:13 +0100 [thread overview]
Message-ID: <6c1bf7ce-1bfa-ec49-8b9c-098c2a0bf37c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_7dbapFgDQeWObejCTqZOUQ9TxaKfwyELGsKMh+dUQuw@mail.gmail.com>
On 30/10/20 21:02, Peter Maydell wrote:
> Having actually looked at the current state of the kernel's
> kernel-doc script I see somebody has already done the
> necessary updates for Sphinx 3 compatibility. So we have
> two choices for 5.2:
> * take this patch 1 as a minimal fix
> * do the sync of the kernel's version of the script
>
> I'll have a look at how painful or otherwise the sync is, I guess.
> We only use the kerneldoc stuff in the 'devel' manual which
> is not really userfacing anyway.
Oh nice! I had a slightly older Linux checkout and it wasn't there yet.
I think you can go ahead with these two patches, I'll take care of the
sync for 6.0.
Here are our two patches.
https://lore.kernel.org/linux-doc/20201030144713.201372-1-pbonzini@redhat.com/T/#t
prev parent reply other threads:[~2020-10-31 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 17:46 [PATCH 0/2] docs: Fix building with Sphinx 3.2 Peter Maydell
2020-10-30 17:46 ` [PATCH 1/2] scripts/kerneldoc: For Sphinx 3 use c:macro for macros with arguments Peter Maydell
2020-10-30 17:49 ` Daniel P. Berrangé
2020-11-02 11:24 ` Stefan Hajnoczi
2020-10-30 17:47 ` [PATCH 2/2] qemu-option-trace.rst.inc: Don't use option:: markup Peter Maydell
2020-10-30 17:48 ` Daniel P. Berrangé
2020-11-02 11:22 ` Stefan Hajnoczi
2020-10-30 18:20 ` [PATCH 0/2] docs: Fix building with Sphinx 3.2 Paolo Bonzini
2020-10-30 19:12 ` Peter Maydell
2020-10-30 20:02 ` Peter Maydell
2020-10-31 14:58 ` Paolo Bonzini [this message]
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=6c1bf7ce-1bfa-ec49-8b9c-098c2a0bf37c@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).