All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Victor Westerhuis <victor@westerhu.is>
Cc: Linux F2FS Dev Mailing List <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH] Fixed a few spelling errors in f2fs-tools
Date: Tue, 17 Nov 2020 08:46:38 -0800	[thread overview]
Message-ID: <20201117164638.GB1636127@google.com> (raw)
In-Reply-To: <f521a968-d946-67b4-5ab4-93e09f7af34a@westerhu.is>

Thanks, I modified a bit and merged.

On 11/12, Victor Westerhuis wrote:
> Dear Mr. Jaegeuk,
> 
> While compiling a newer version of f2fs-tools for Debian, Lintian found
> some spelling errors. I have corrected them using the patch below, which
> should apply cleanly on top of dev.
> 
> Kind regards,
> 
> 
> Victor Westerhuis
> 
> ---
>  fsck/mount.c          | 2 +-
>  man/defrag.f2fs.8     | 2 +-
>  man/mkfs.f2fs.8       | 2 +-
>  tools/f2fs_io_parse.c | 2 +-
>  tools/f2fscrypt.8     | 2 +-
>  5 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/fsck/mount.c b/fsck/mount.c
> index 8ebc5b0..fc3ecb9 100644
> --- a/fsck/mount.c
> +++ b/fsck/mount.c
> @@ -2482,7 +2482,7 @@ void rewrite_sit_area_bitmap(struct f2fs_sb_info *sbi)
>                 se->valid_blocks = valid_blocks;
>                 type = se->type;
>                 if (type >= NO_CHECK_TYPE) {
> -                       ASSERT_MSG("Invalide type and valid blocks=%x,%x",
> +                       ASSERT_MSG("Invalid type and valid blocks=%x,%x",
>                                         segno, valid_blocks);
>                         type = 0;
>                 }
> diff --git a/man/defrag.f2fs.8 b/man/defrag.f2fs.8
> index b08399b..34113de 100644
> --- a/man/defrag.f2fs.8
> +++ b/man/defrag.f2fs.8
> @@ -48,7 +48,7 @@ is 0 on success and -1 on failure.
>  Specify the starting block address.
>  .TP
>  .BI \-l " number of blocks"
> -Specifiy the number of blocks to move.
> +Specify the number of blocks to move.
>  .TP
>  .BI \-t " target block address"
>  Specify the destination block address.
> diff --git a/man/mkfs.f2fs.8 b/man/mkfs.f2fs.8
> index 85b6019..0aca4dc 100644
> --- a/man/mkfs.f2fs.8
> +++ b/man/mkfs.f2fs.8
> @@ -98,7 +98,7 @@ mkfs.f2fs \- create an F2FS file system
>  is used to create a f2fs file system (usually in a disk partition).
>  \fIdevice\fP is the special file corresponding to the device (e.g.
>  \fI/dev/sdXX\fP).
> -\fIsectors\fP is optionally given for specifing the filesystem size.
> +\fIsectors\fP is optionally given for specifying the filesystem size.
>  .PP
>  The exit code returned by
>  .B mkfs.f2fs
> diff --git a/tools/f2fs_io_parse.c b/tools/f2fs_io_parse.c
> index d146ead..47f1194 100644
> --- a/tools/f2fs_io_parse.c
> +++ b/tools/f2fs_io_parse.c
> @@ -271,7 +271,7 @@ static void __print_ftype()
>         int i;
>         setlocale(LC_ALL, "");
> -       printf("\n===== Data R/W in 4KB accoring to File types =====\n");
> +       printf("\n===== Data R/W in 4KB according to File types =====\n");
>         for (i = 0; i < __NR_FILES; i++)
>                 printf(" %17s |", file_type_string[i]);
>         printf("\n");
> diff --git a/tools/f2fscrypt.8 b/tools/f2fscrypt.8
> index a60adc8..5e2258a 100644
> --- a/tools/f2fscrypt.8
> +++ b/tools/f2fscrypt.8
> @@ -40,7 +40,7 @@ identifier consisting of 16 hexadecimal characters.
>  The target directory must be empty.
>  .SH EXAMPLE
>  .nf
> -Formats a f2fs filesytem that supports encrypt.
> +Formats a f2fs filesystem that supports encrypt.
>  .ft R
>  # mkfs.f2fs -O encrypt /dev/sdxx
> -- 
> 2.28.0
> 





_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

           reply	other threads:[~2020-11-17 16:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <f521a968-d946-67b4-5ab4-93e09f7af34a@westerhu.is>]

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=20201117164638.GB1636127@google.com \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=victor@westerhu.is \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.