All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Xinhai <lixinhai.lxh@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] Doc: page_migration: fix numbering for non-LRU movable flags
Date: Thu, 9 Sep 2021 09:20:28 +0800	[thread overview]
Message-ID: <f6efb4d9-55cb-f782-cfcb-75e6a2dd9285@gmail.com> (raw)
In-Reply-To: <87mtomq1hb.fsf@meer.lwn.net>



On 9/9/21 4:03 AM, Jonathan Corbet wrote:
> Li Xinhai <lixinhai.lxh@gmail.com> writes:
> 
>> The non-LRU movable flags part is not relevant to above 3 funcitons, so remove
>> the number 4.
>>
>> Signed-off-by: Li Xinhai <lixinhai.lxh@gmail.com>
>>
>> ---
>>   Documentation/vm/page_migration.rst | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/vm/page_migration.rst b/Documentation/vm/page_migration.rst
>> index db9d7e5539cb..08810f549f70 100644
>> --- a/Documentation/vm/page_migration.rst
>> +++ b/Documentation/vm/page_migration.rst
>> @@ -205,7 +205,7 @@ which are function pointers of struct address_space_operations.
>>      In this function, the driver should put the isolated page back into its own data
>>      structure.
>>   
>> -4. non-LRU movable page flags
>> +Non-LRU movable page flags
> 
> So should this be a section heading instead?
No. This line and the following content still belong to its current section, so only
need remove '4.', and 'non'-> 'Non'.

>
> Thanks,
> 
> jon
> 

  reply	other threads:[~2021-09-09  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 14:52 [PATCH] Doc: page_migration: fix numbering for non-LRU movable flags Li Xinhai
2021-09-08 20:03 ` Jonathan Corbet
2021-09-09  1:20   ` Li Xinhai [this message]
2021-09-14 20:54 ` Jonathan Corbet

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=f6efb4d9-55cb-f782-cfcb-75e6a2dd9285@gmail.com \
    --to=lixinhai.lxh@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.