From: JunChao Sun <sunjunchao2870@gmail.com>
To: linux-ext4@vger.kernel.org, linux-doc@vger.kernel.org
Cc: tytso@mit.edu, corbet@lwn.net, JunChao Sun <sunjunchao2870@gmail.com>
Subject: [PATCH] Documentation: ext4: correct the document about superblock
Date: Sun, 14 Aug 2022 02:00:16 -0700 [thread overview]
Message-ID: <20220814090016.3160-1-sunjunchao2870@gmail.com> (raw)
Correct some questions like this:
s_lastcheck_hi field should be upper 8 bits of the
s_lastcheck field, rather than itself.
Signed-off-by: JunChao Sun <sunjunchao2870@gmail.com>
---
Documentation/filesystems/ext4/super.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/ext4/super.rst b/Documentation/filesystems/ext4/super.rst
index 268888522e35..0152888cac29 100644
--- a/Documentation/filesystems/ext4/super.rst
+++ b/Documentation/filesystems/ext4/super.rst
@@ -456,15 +456,15 @@ The ext4 superblock is laid out as follows in
* - 0x277
- __u8
- s_lastcheck_hi
- - Upper 8 bits of the s_lastcheck_hi field.
+ - Upper 8 bits of the s_lastcheck field.
* - 0x278
- __u8
- s_first_error_time_hi
- - Upper 8 bits of the s_first_error_time_hi field.
+ - Upper 8 bits of the s_first_error_time field.
* - 0x279
- __u8
- s_last_error_time_hi
- - Upper 8 bits of the s_last_error_time_hi field.
+ - Upper 8 bits of the s_last_error_time field.
* - 0x27A
- __u8
- s_pad[2]
--
2.17.1
next reply other threads:[~2022-08-14 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 9:00 JunChao Sun [this message]
2022-08-15 9:21 ` [PATCH] Documentation: ext4: correct the document about superblock Bagas Sanjaya
2022-08-15 12:37 ` JunChao Sun
-- strict thread matches above, loose matches on Subject: below --
2022-08-15 12:52 JunChao Sun
2022-08-15 14:24 ` Darrick J. Wong
2022-08-29 16:26 ` 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=20220814090016.3160-1-sunjunchao2870@gmail.com \
--to=sunjunchao2870@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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