Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <e41096bb-1911-3d91-119a-8cdf55135673@infradead.org>
Date:   Mon, 24 Jul 2023 22:16:45 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: linux-next: build warning after merge of the mm-hotfixes tree
Content-Language: en-US
To:     Hugh Dickins <hughd@google.com>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20230725135546.28334fe4@canb.auug.org.au>
 <3084e97c-3a7d-ace8-2e9c-31642fd663df@google.com>
From:   Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <3084e97c-3a7d-ace8-2e9c-31642fd663df@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 7/24/23 21:10, Hugh Dickins wrote:
> 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!

Hi Hugh,

I have a patch ready. I'll send it in a few minutes.

-- 
~Randy