linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <djwong@kernel.org>,
	David Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the xfs tree
Date: Mon, 8 Feb 2021 23:44:31 +1100	[thread overview]
Message-ID: <20210208234431.54e51b57@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

Hi all,

After merging the xfs tree, today's linux-next build (htmldocs) produced
this warning:

Documentation/admin-guide/xfs.rst:531: WARNING: Malformed table.
No bottom table border found or no blank line after table bottom.

============     ===========
  Knob           Description
============     ===========
Documentation/admin-guide/xfs.rst:534: WARNING: Blank line required after table.
Documentation/admin-guide/xfs.rst:536: WARNING: Definition list ends without a blank line; unexpected unindent.
Documentation/admin-guide/xfs.rst:538: WARNING: Unexpected indentation.

Introduced by commit

  f83d436aef5d ("xfs: increase the default parallelism levels of pwork clients")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-02-08 12:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 12:44 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23  4:36 linux-next: build warning after merge of the xfs tree Stephen Rothwell
2024-02-23  6:35 ` Christoph Hellwig
2024-02-23  8:55   ` Mauro Carvalho Chehab
2024-02-23 14:06     ` Christoph Hellwig
2024-02-24  9:07       ` Akira Yokosawa
2024-02-26 10:57         ` Christoph Hellwig
2021-06-07  0:48 Stephen Rothwell
2021-06-07  1:15 ` Dave Chinner
2021-01-24 22:55 Stephen Rothwell
2021-01-25 13:26 ` Brian Foster
2021-01-27  3:14   ` Darrick J. Wong
2020-05-08  1:15 Stephen Rothwell
2020-01-16  0:37 Stephen Rothwell
2020-01-15 22:12 Stephen Rothwell
2020-01-24  2:47 ` Stephen Rothwell
2020-01-24  4:17   ` Darrick J. Wong
2017-10-31 22:42 Stephen Rothwell
2017-08-31  0:07 Stephen Rothwell
2017-08-31 10:30 ` Brian Foster
2017-08-31 14:57   ` Darrick J. Wong
2017-08-31 15:22     ` Brian Foster
2017-08-31 15:41       ` Darrick J. Wong
2017-08-31 21:32       ` Dave Chinner
2010-03-04  0:19 Stephen Rothwell

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=20210208234431.54e51b57@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@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).