From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Hugh Dickins <hughd@google•com>,
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 mm-hotfixes tree
Date: Tue, 25 Jul 2023 13:55:46 +1000 [thread overview]
Message-ID: <20230725135546.28334fe4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Hi all,
After merging the mm-hotfixes tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/filesystems/tmpfs.rst:116: ERROR: Malformed table.
Text in column margin in table line 4.
=========== ==============================================================
huge=never Do not allocate huge pages. This is the default.
huge=always Attempt to allocate huge page every time a new page is needed.
huge=within_size Only allocate huge page if it will be fully within i_size.
Also respect madvise(2) hints.
huge=advise Only allocate huge page if requested with madvise(2).
=========== ==============================================================
Introduced by commit
a0ebb5aa2de3 ("tmpfs: fix Documentation of noswap and huge mount options")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-07-25 3:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 3:55 Stephen Rothwell [this message]
2023-07-25 4:10 ` linux-next: build warning after merge of the mm-hotfixes tree Hugh Dickins
2023-07-25 5:16 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2024-04-16 7:35 Stephen Rothwell
2024-04-16 18:51 ` Andrew Morton
2024-04-17 5:29 ` Stephen Rothwell
2024-04-17 20:53 ` Andrew Morton
2024-08-08 3:58 Stephen Rothwell
2024-08-08 4:06 ` Pasha Tatashin
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=20230725135546.28334fe4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=hughd@google$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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