From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org
Subject: Patches for a Documentation quick-fix pull request to Linus
Date: Fri, 5 Feb 2021 12:30:50 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2102051224330.19658@felia> (raw)
Hi Jonathan,
on the current mainline repository, we currently have the following
warnings with make htmldocs:
./Documentation/virt/kvm/api.rst:4537: WARNING: Unexpected indentation.
./Documentation/virt/kvm/api.rst:4539: WARNING: Block quote ends without a blank line; unexpected unindent.
./Documentation/ABI/testing/sysfs-firmware-sgi_uv:2: WARNING: Unexpected indentation.
Mauro has already created patches to address them, but these patches here
have not been picked up by the other subsystem maintainers (within the
last three weeks):
a5a20cd7ff9870b5316825fa1abad0b867832700.1610610444.git.mchehab+huawei@kernel.org
452854f2dd0625b9fee33b9f5e29343d6149781e.1610610444.git.mchehab+huawei@kernel.org
Jonathan, could you pick those two patches and provide them as a
Documentation quick-fix pull request to Linus?
With that, we are back to zero warnings on mainline.
Just for your information, for linux-next, as of next-20210204, with the
further already submitted patches, make htmldocs
has zero warnings:
a5a20cd7ff9870b5316825fa1abad0b867832700.1610610444.git.mchehab+huawei@kernel.org
452854f2dd0625b9fee33b9f5e29343d6149781e.1610610444.git.mchehab+huawei@kernel.org
84693a4901efb553dd95fe4909b50d6d8faf8107.1610610444.git.mchehab+huawei@kernel.org
20210204180059.28360-1-lukas.bulwahn@gmail.com
20210205095506.29146-1-lukas.bulwahn@gmail.com
So, we are in a good shape for zero-warning documentation build with the
next -rc1 if those patches are being
picked up in the next few days.
Thanks,
Lukas
reply other threads:[~2021-02-05 11:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.21.2102051224330.19658@felia \
--to=lukas.bulwahn@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+huawei@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