linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Avinesh Kumar <akumar@suse.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 2/2] inode.7: correct the field name for number of blocks
Date: Wed, 13 Sep 2023 16:17:42 +0200	[thread overview]
Message-ID: <7e813d02-30cc-468f-9753-00a435cf2b3f@kernel.org> (raw)
In-Reply-To: <20230829103004.18459-2-akumar@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 920 bytes --]

Hi Avinesh,

On 2023-08-29 12:30, Avinesh Kumar wrote:
> Fixes: b48c75727c64 ("inode.7: New page with information about inodes")
> Signed-off-by: Avinesh Kumar <akumar@suse.de>

Patch set applied.

Thanks,
Alex

> ---
>  man7/inode.7 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man7/inode.7 b/man7/inode.7
> index 5140fb069..7b7e4dcd9 100644
> --- a/man7/inode.7
> +++ b/man7/inode.7
> @@ -98,7 +98,7 @@ This field gives the "preferred" blocksize for efficient filesystem I/O.
>  an inefficient read-modify-rewrite.)
>  .TP
>  Number of blocks allocated to the file
> -\fIstat.st_blocks\fP; \fIstatx.stx_size\fP
> +\fIstat.st_blocks\fP; \fIstatx.stx_blocks\fP
>  .IP
>  This field indicates the number of blocks allocated to the file,
>  512-byte units,

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-09-13 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 10:30 [PATCH v2 1/2] inode.7: Remove duplicate field name Avinesh Kumar
2023-08-29 10:30 ` [PATCH v2 2/2] inode.7: correct the field name for number of blocks Avinesh Kumar
2023-09-13 14:17   ` Alejandro Colomar [this message]

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=7e813d02-30cc-468f-9753-00a435cf2b3f@kernel.org \
    --to=alx@kernel.org \
    --cc=akumar@suse.de \
    --cc=linux-man@vger.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).