From: Zach Carter <z.carter@f5.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfsck: Exit and print error message when not able to open device
Date: Tue, 20 Jan 2009 11:26:00 -0800 [thread overview]
Message-ID: <200901201126.00699.z.carter@f5.com> (raw)
In-Reply-To: <1232152077-3862-1-git-send-email-cascardo@holoscopio.com>
On Friday 16 January 2009 16:27:57 Thadeu Lima de Souza Cascardo wrote:
> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 fprintf (stderr, "Coult not open %s\n",=
filename);
"Coult" should be "Could".
Other than that, the patch seems to fix the segfault issue for me.
thanks,
-Zach
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-01-20 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 0:27 [PATCH] btrfsck: Exit and print error message when not able to open device Thadeu Lima de Souza Cascardo
2009-01-20 19:26 ` Zach Carter [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=200901201126.00699.z.carter@f5.com \
--to=z.carter@f5.com \
--cc=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