linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
	linux-btrfs@vger.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	rdunlap@infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 05/10] inode.c: Couple of typo fixes
Date: Sun, 28 Mar 2021 09:48:29 +0530	[thread overview]
Message-ID: <b4ed7b980b45d5d8bd398df1316db4918aa195b7.1616904353.git.unixbhaskar@gmail.com> (raw)
In-Reply-To: <cover.1616904353.git.unixbhaskar@gmail.com>

s/contaning/containing/
s/clearning/clearing/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
 fs/btrfs/inode.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index a520775949a0..dd7cc65db7bd 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -2784,8 +2784,8 @@ static int insert_reserved_file_extent(struct btrfs_trans_handle *trans,
 	/*
 	 * If we dropped an inline extent here, we know the range where it is
 	 * was not marked with the EXTENT_DELALLOC_NEW bit, so we update the
-	 * number of bytes only for that range contaning the inline extent.
-	 * The remaining of the range will be processed when clearning the
+	 * number of bytes only for that range containing the inline extent.
+	 * The remaining of the range will be processed when clearing the
 	 * EXTENT_DELALLOC_BIT bit through the ordered extent completion.
 	 */
 	if (file_pos == 0 && !IS_ALIGNED(drop_args.bytes_found, sectorsize)) {
--
2.26.2


  parent reply	other threads:[~2021-03-28  4:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  4:18 [PATCH 00/10] BTRFS: Mundane typo fixes Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 01/10] extent-map-tests.c: A typo fix Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 02/10] dev-replace.c: " Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 03/10] ioctl.c: " Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 04/10] zoned.c: " Bhaskar Chowdhury
2021-03-28  4:18 ` Bhaskar Chowdhury [this message]
2021-03-28  4:18 ` [PATCH 06/10] scrub.c: Fix a typo Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 07/10] locking.c: Fix same typo in couple of places Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 08/10] volumes.c: Fix a typo Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 09/10] extent-tree.c: " Bhaskar Chowdhury
2021-03-28  4:18 ` [PATCH 10/10] disk-io.c: " Bhaskar Chowdhury

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=b4ed7b980b45d5d8bd398df1316db4918aa195b7.1616904353.git.unixbhaskar@gmail.com \
    --to=unixbhaskar@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@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).