linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: baihaowen@meizu.com
Cc: alexs@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, seakeel@gmail.com,
	siyanteng01@gmail.com, siyanteng@loongson.cn
Subject: Re: [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion
Date: Sun, 24 Apr 2022 12:38:10 +0900	[thread overview]
Message-ID: <3ce4feb9-5477-e7fb-e98c-3d6342ddc7b5@gmail.com> (raw)
In-Reply-To: <1650424016-7225-3-git-send-email-baihaowen@meizu.com>

Hi,

Wed, 20 Apr 2022 11:06:56 +0800,
baihaowen wrote:
> After make htmldocs, the table which is made of tab will
> display all by one line. so we make a standard table for STANDARD
> FORMAT SPECIFIERS description.
> 
> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
> ---
>  Documentation/vm/page_owner.rst | 34 ++++++++++++++++++++--------------
>  1 file changed, 20 insertions(+), 14 deletions(-)
> 
> diff --git a/Documentation/vm/page_owner.rst b/Documentation/vm/page_owner.rst
> index 422d5fa99e84..a8505e3a3044 100644
> --- a/Documentation/vm/page_owner.rst
> +++ b/Documentation/vm/page_owner.rst
> @@ -174,22 +174,28 @@ STANDARD FORMAT SPECIFIERS
>  
>  For --sort option:
>  
> -	KEY		LONG		DESCRIPTION
> -	p		pid		process ID
> -	tg		tgid		thread group ID
> -	n		name		task command name
> -	st		stacktrace	stack trace of the page allocation
> -	T		txt		full text of block
> -	ft		free_ts		timestamp of the page when it was released
> -	at		alloc_ts	timestamp of the page when it was allocated
> +        ====            ==========      ============================================
> +        KEY             LONG            DESCRIPTION
> +        ====            ==========      ============================================
> +        p               pid             process ID
> +        tg              tgid            thread group ID
> +        n               name            task command name
> +        st              stacktrace      stack trace of the page allocation
> +        T               txt             full text of block
> +        ft              free_ts         timestamp of the page when it was released
> +        at              alloc_ts        timestamp of the page when it was allocated
>          ator            allocator       memory allocator for pages
> +        ====            ==========      ============================================
>  
>  For --curl option:
>  
> -	KEY		LONG		DESCRIPTION
> -	p		pid		process ID
> -	tg		tgid		thread group ID
> -	n		name		task command name
> -	f		free		whether the page has been released or not
> -	st		stacktrace	stack trace of the page allocation
> +        ====            ===========     ============================================
> +        KEY             LONG            DESCRIPTION
> +        ====            ===========     ============================================
> +        p               pid             process ID
> +        tg              tgid            thread group ID
> +        n               name            task command name
> +        f               free            whether the page has been released or not
> +        st              stacktrace      stack trace of the page allocation
>          ator            allocator       memory allocator for pages
> +        ====            ===========     ============================================

This patch looks like against akpm's tree (or linux-next).
So it is not applicable to docs-next of Jonathan's tree at the
moment.

You need to wait until docs-next catches up akpm's tree.

Patch 1/2 should wait until the English doc is updated,
I suppose.

By the way, I don't think the list of options need tables.
Literal blocks should suffice.

I mean, How about the simpler changes:

>  For --sort option:
   For --sort option::

>  For --curl option:
   For --curl option::

Thoughts?

       Thanks, Akira

> -- 
> 2.7.4


  parent reply	other threads:[~2022-04-24  3:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  1:30 [PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst 司延腾
2022-04-15  2:09 ` yanteng si
2022-04-18  1:58   ` yanteng si
2022-04-18  9:28     ` [PATCH V4] " Haowen Bai
2022-04-18 12:41       ` Alex Shi
2022-04-19  1:23         ` Haowen Bai
2022-04-19  1:46           ` yanteng si
2022-04-19  2:07             ` [PATCH V5] " Haowen Bai
2022-04-19  2:33               ` yanteng si
2022-04-19  3:24                 ` baihaowen
2022-04-19  3:34                   ` [PATCH V6] " Haowen Bai
2022-04-19  4:27                   ` [PATCH V5] " Alex Shi
2022-04-19  5:49                     ` [PATCH V7] " Haowen Bai
2022-04-19  7:34                       ` [PATCH V8] " Haowen Bai
2022-04-19 14:42                         ` yanteng si
2022-04-20  3:06                           ` [PATCH 0/2] " Haowen Bai
2022-04-20  3:06                             ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
2022-04-23 10:27                               ` Alex Shi
2022-04-24  2:56                                 ` baihaowen
2022-04-24  3:16                                   ` Alex Shi
2022-04-25  1:17                                     ` baihaowen
2022-04-25  3:19                                       ` yanteng si
2022-04-25  8:18                                         ` baihaowen
2022-04-26  6:57                                           ` yanteng si
2022-04-26  8:20                                       ` Alex Shi
2022-04-26  8:23                                         ` baihaowen
     [not found]                                           ` <3f93bb0d-5658-f269-f8cc-d0a964ffb68b@gmail.com>
2022-04-26  8:30                                             ` baihaowen
2022-04-20  3:06                             ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
2022-04-20 12:31                               ` Bagas Sanjaya
2022-04-20 12:46                                 ` Jonathan Corbet
2022-04-24  3:38                               ` Akira Yokosawa [this message]
2022-04-24  5:24                                 ` Jonathan Corbet
2022-04-26  8:39                                 ` Alex Shi
2022-04-21 12:26                             ` [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst yanteng si
2022-04-22  1:40                               ` baihaowen
2022-04-22  2:35                                 ` Akira Yokosawa
2022-04-19  1:24         ` [PATCH V4] docs/zh_CN: " baihaowen
2022-04-18  9:29     ` [PATCH V3] " baihaowen
     [not found] <1650956694-30699-1-git-send-email-baihaowen@meizu.com>
2022-04-26  7:04 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
  -- strict thread matches above, loose matches on Subject: below --
2022-04-26  7:07 [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst Haowen Bai
2022-04-26  7:07 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai

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=3ce4feb9-5477-e7fb-e98c-3d6342ddc7b5@gmail.com \
    --to=akiyks@gmail.com \
    --cc=alexs@kernel.org \
    --cc=baihaowen@meizu.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    /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).