linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Gao Mingfei <g199209@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	trivial@kernel.org, Gao Mingfei <g199209@gmail.com>
Subject: Re: [PATCH] docs: block: fix stat.rst document error
Date: Fri, 04 Jun 2021 11:26:50 -0600	[thread overview]
Message-ID: <87eedhilr9.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210601085145.3273-1-g199209@gmail.com>

Gao Mingfei <g199209@gmail.com> writes:

> There are 17 decimal vaules, not 11.
>
> Previous committers forgot to change this number when adding
> new fields.
>
> Signed-off-by: Gao Mingfei <g199209@gmail.com>
> ---
>  Documentation/block/stat.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/block/stat.rst b/Documentation/block/stat.rst
> index 77311335c08b..a1cd9db2058f 100644
> --- a/Documentation/block/stat.rst
> +++ b/Documentation/block/stat.rst
> @@ -18,7 +18,7 @@ A.
>     each, it would be impossible to guarantee that a set of readings
>     represent a single point in time.
>  
> -The stat file consists of a single line of text containing 11 decimal
> +The stat file consists of a single line of text containing 17 decimal
>  values separated by whitespace.  The fields are summarized in the
>  following table, and described in more detail below.

I've applied this.  I rewrote the changelog, though, to better fit
kernel style:

	Update the description of the device stat files to include the
        proper number of fields.

Thanks,

jon

  reply	other threads:[~2021-06-04 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  8:51 [PATCH] docs: block: fix stat.rst document error Gao Mingfei
2021-06-04 17:26 ` Jonathan Corbet [this message]
2021-06-07  1:56   ` 高明飞

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=87eedhilr9.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=g199209@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.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 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).