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 04/10] zoned.c: A typo fix
Date: Sun, 28 Mar 2021 09:48:28 +0530 [thread overview]
Message-ID: <7eb66663f50d873df4a7290ed316802885729c30.1616904353.git.unixbhaskar@gmail.com> (raw)
In-Reply-To: <cover.1616904353.git.unixbhaskar@gmail.com>
s/beggining/beginning/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
fs/btrfs/zoned.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
index 1f972b75a9ab..d6cd0d4eb1a9 100644
--- a/fs/btrfs/zoned.c
+++ b/fs/btrfs/zoned.c
@@ -383,7 +383,7 @@ int btrfs_get_dev_zone_info(struct btrfs_device *device)
}
/*
- * If zones[0] is conventional, always use the beggining of the
+ * If zones[0] is conventional, always use the beginning of the
* zone to record superblock. No need to validate in that case.
*/
if (zone_info->sb_zones[BTRFS_NR_SB_LOG_ZONES * i].type ==
--
2.26.2
next prev 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 ` Bhaskar Chowdhury [this message]
2021-03-28 4:18 ` [PATCH 05/10] inode.c: Couple of typo fixes Bhaskar Chowdhury
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=7eb66663f50d873df4a7290ed316802885729c30.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).