From: Avinesh Kumar <akumar@suse.de>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org
Subject: [PATCH 2/2] inode.7: correct the field name for number of blocks
Date: Tue, 29 Aug 2023 14:33:31 +0530 [thread overview]
Message-ID: <20230829090335.14051-2-akumar@suse.de> (raw)
In-Reply-To: <20230829090335.14051-1-akumar@suse.de>
Signed-off-by: Avinesh Kumar <akumar@suse.de>
---
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,
--
2.41.0
next prev parent reply other threads:[~2023-08-29 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 9:03 [PATCH 1/2] inode.7: Remove duplicate field name Avinesh Kumar
2023-08-29 9:03 ` Avinesh Kumar [this message]
2023-08-29 9:50 ` [PATCH 2/2] inode.7: correct the field name for number of blocks Alejandro Colomar
2023-08-29 9:46 ` [PATCH 1/2] inode.7: Remove duplicate field name Alejandro Colomar
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=20230829090335.14051-2-akumar@suse.de \
--to=akumar@suse.de \
--cc=alx@kernel.org \
--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).