From: Jan Kara <jack@suse.cz>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@suse.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext2: ext2.h: fix duplicated word + typos
Date: Mon, 27 Jul 2020 10:58:17 +0200 [thread overview]
Message-ID: <20200727085817.GF23179@quack2.suse.cz> (raw)
In-Reply-To: <20200720001327.23603-1-rdunlap@infradead.org>
On Sun 19-07-20 17:13:27, Randy Dunlap wrote:
> Change the repeated word "the" in "it the the" to "it is the".
> Fix typo "recentl" to "recently".
> Fix verb "give" to "gives".
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jan Kara <jack@suse.com>
> Cc: linux-ext4@vger.kernel.org
Thanks! Applied.
Honza
> ---
> fs/ext2/ext2.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20200717.orig/fs/ext2/ext2.h
> +++ linux-next-20200717/fs/ext2/ext2.h
> @@ -52,8 +52,8 @@ struct ext2_block_alloc_info {
> /*
> * Was i_next_alloc_goal in ext2_inode_info
> * is the *physical* companion to i_next_alloc_block.
> - * it the the physical block number of the block which was most-recentl
> - * allocated to this file. This give us the goal (target) for the next
> + * it is the physical block number of the block which was most-recently
> + * allocated to this file. This gives us the goal (target) for the next
> * allocation when we detect linearly ascending requests.
> */
> ext2_fsblk_t last_alloc_physical_block;
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-07-27 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 0:13 [PATCH] ext2: ext2.h: fix duplicated word + typos Randy Dunlap
2020-07-27 8:58 ` Jan Kara [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=20200727085817.GF23179@quack2.suse.cz \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).