From: Adam Borowski <kilobyte@angband.pl>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Cc: Adam Borowski <kilobyte@angband.pl>
Subject: [PATCH] btrfs-progs: check: typo in an error message: "boudnary"
Date: Fri, 27 Mar 2020 01:55:05 +0100 [thread overview]
Message-ID: <20200327005505.126534-1-kilobyte@angband.pl> (raw)
Signed-off-by: Adam Borowski <kilobyte@angband.pl>
---
check/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/check/main.c b/check/main.c
index 4115049a..484b0729 100644
--- a/check/main.c
+++ b/check/main.c
@@ -8640,7 +8640,7 @@ static int check_dev_extents(struct btrfs_fs_info *fs_info)
}
if (physical_offset + physical_len > dev->total_bytes) {
error(
-"dev extent devid %llu physical offset %llu len %llu is beyond device boudnary %llu",
+"dev extent devid %llu physical offset %llu len %llu is beyond device boundary %llu",
devid, physical_offset, physical_len,
dev->total_bytes);
ret = -EUCLEAN;
--
2.26.0
next reply other threads:[~2020-03-27 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 0:55 Adam Borowski [this message]
2020-03-27 1:04 ` [PATCH] btrfs-progs: check: typo in an error message: "boudnary" Marcos Paulo de Souza
2020-03-27 15:17 ` David Sterba
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=20200327005505.126534-1-kilobyte@angband.pl \
--to=kilobyte@angband.pl \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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).