From: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
To: linux-btrfs@vger.kernel.org
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Subject: [PATCH] Fix typo: s/Coult/Could/
Date: Fri, 23 Jan 2009 19:14:47 -0200 [thread overview]
Message-ID: <1232745288-4307-1-git-send-email-cascardo@holoscopio.com> (raw)
Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
---
disk-io.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/disk-io.c b/disk-io.c
index e49c220..9e0cfe8 100644
--- a/disk-io.c
+++ b/disk-io.c
@@ -530,7 +530,7 @@ struct btrfs_root *open_ctree(const char *filename, u64 sb_bytenr, int writes)
fp = open(filename, flags, 0600);
if (fp < 0) {
- fprintf (stderr, "Coult not open %s\n", filename);
+ fprintf (stderr, "Could not open %s\n", filename);
return NULL;
}
root = open_ctree_fd(fp, filename, sb_bytenr, writes);
--
1.6.0.6
next reply other threads:[~2009-01-23 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 21:14 Thadeu Lima de Souza Cascardo [this message]
2009-01-23 21:14 ` [PATCH] Add error message explaining why opening a device failed Thadeu Lima de Souza Cascardo
2009-01-24 3:39 ` [PATCH] btrfs_progs/mkfs.c more input data verification cleanup ashford
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=1232745288-4307-1-git-send-email-cascardo@holoscopio.com \
--to=cascardo@holoscopio.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