public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: I Hsin Cheng <richard120310@gmail.com>, tytso@mit.edu
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
	I Hsin Cheng <richard120310@gmail.com>
Subject: Re: [PATCH] docs: ext4: Ammend white space
Date: Tue, 22 Apr 2025 07:30:39 -0600	[thread overview]
Message-ID: <87zfg8uxvk.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250422055702.451729-1-richard120310@gmail.com>

I Hsin Cheng <richard120310@gmail.com> writes:

> There should be a white space between the words "block" and "size",
> instead of writing them together as "blocksize". Ammend a white space
> between them.
>
> Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
> ---
>  Documentation/filesystems/ext4/blockgroup.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/ext4/blockgroup.rst b/Documentation/filesystems/ext4/blockgroup.rst
> index ed5a5cac6d40..32a66a956f31 100644
> --- a/Documentation/filesystems/ext4/blockgroup.rst
> +++ b/Documentation/filesystems/ext4/blockgroup.rst
> @@ -108,7 +108,7 @@ block groups which can be described by a single block group descriptor
>  block. Since the size of the block group descriptor structure is 64
>  bytes, a meta-block group contains 16 block groups for filesystems with
>  a 1KB block size, and 64 block groups for filesystems with a 4KB
> -blocksize. Filesystems can either be created using this new block group
> +block size. Filesystems can either be created using this new block group
>  descriptor layout, or existing filesystems can be resized on-line, and
>  the field s_first_meta_bg in the superblock will indicate the first
>  block group using this new layout.

Thank you for working to improve the documentation!

If you dig through our documentation, you will see that "blocksize" is
fairly common usage.  Changing them all will result in a fair amount of
churn without much in the way of benefit in either readability or
accuracy.  May I politely suggest focusing on the many real problems our
documentation has instead?

Thanks,

jon

      reply	other threads:[~2025-04-22 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  5:57 [PATCH] docs: ext4: Ammend white space I Hsin Cheng
2025-04-22 13:30 ` Jonathan Corbet [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=87zfg8uxvk.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard120310@gmail.com \
    --cc=skhan@linuxfoundation.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