From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Adam Bratschi-Kaye <ark.email@gmail.com>,
Alex Gaynor <alex.gaynor@gmail.com>,
Boris-Chengbiao Zhou <bobo1239@web.de>, Daniel Xu <dxu@dxuuu.xyz>,
Finn Behrens <me@kloenk.de>, Gary Guo <gary@garyguo.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Miguel Ojeda <ojeda@kernel.org>,
Sven Van Asbroeck <thesven73@gmail.com>,
Wedson Almeida Filho <wedsonaf@google.com>,
Wei Liu <wei.liu@kernel.org>, Wu XiangCheng <bobwxc@email.cn>,
Yuki Okushi <jtitor@2k36.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the rust tree
Date: Fri, 11 Feb 2022 18:49:45 +1100 [thread overview]
Message-ID: <20220211184945.7b2fb872@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Hi all,
After merging the rust tree, today's linux-next build (htmldocs) produced
these warnings:
Documentation/rust/coding-guidelines.rst:74: WARNING: Unexpected indentation.
Documentation/rust/coding-guidelines.rst:79: WARNING: Definition list ends without a blank line; unexpected unindent.
Documentation/rust/coding-guidelines.rst:80: WARNING: Block quote ends without a blank line; unexpected unindent.
Introduced by commit
0b154fdfa6ec ("docs: add Rust documentation")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-02-11 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 7:49 Stephen Rothwell [this message]
2022-02-11 19:59 ` Miguel Ojeda
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=20220211184945.7b2fb872@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alex.gaynor@gmail.com \
--cc=ark.email@gmail.com \
--cc=bobo1239@web.de \
--cc=bobwxc@email.cn \
--cc=dxu@dxuuu.xyz \
--cc=gary@garyguo.net \
--cc=jtitor@2k36.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=me@kloenk.de \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=ojeda@kernel.org \
--cc=thesven73@gmail.com \
--cc=wedsonaf@google.com \
--cc=wei.liu@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
all inboxes | Powered by JetHome®