From: Hugh Dickins <hughd@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-hotfixes tree
Date: Mon, 24 Jul 2023 21:10:59 -0700 (PDT) [thread overview]
Message-ID: <3084e97c-3a7d-ace8-2e9c-31642fd663df@google.com> (raw)
In-Reply-To: <20230725135546.28334fe4@canb.auug.org.au>
On Tue, 25 Jul 2023, Stephen Rothwell wrote:
> 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")
Sorry about that, Stephen: thanks for the report.
Randy, you're always my goto guy for how to get these Doc things right,
I hope you don't mind. I just write the text as I want it to appear,
then get caught out by unfamiliar rules.
Please suggest a fixup to the fix patch if you can - thanks!
Hugh
next prev parent reply other threads:[~2023-07-25 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 3:55 linux-next: build warning after merge of the mm-hotfixes tree Stephen Rothwell
2023-07-25 4:10 ` Hugh Dickins [this message]
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
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=3084e97c-3a7d-ace8-2e9c-31642fd663df@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).