linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BUG while writing to USB btrfs filesystem
Date: Mon, 31 Jan 2011 14:35:03 +1100	[thread overview]
Message-ID: <4D462DE7.7050502@csamuel.org> (raw)
In-Reply-To: <AANLkTinFq=EfJDU6EUTGN6J9rP2aw849o+KvGV_C-L4G@mail.gmail.com>

On 31/01/11 14:11, cwillu wrote:

> There's a bunch of places it could be (any ret = foo
> followed by a break will exit with that ret rather
> than oops).

Ahh, thanks for that, I plead being a sysadmin rather than
a programmer.. ;-)

-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

  reply	other threads:[~2011-01-31  3:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 22:28 BUG while writing to USB btrfs filesystem cwillu
2011-01-18 23:06 ` cwillu
2011-01-31  1:33   ` cwillu
2011-01-31  2:57     ` Chris Samuel
2011-01-31  3:11       ` cwillu
2011-01-31  3:35         ` Chris Samuel [this message]
2011-01-31  5:18           ` cwillu

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=4D462DE7.7050502@csamuel.org \
    --to=chris@csamuel.org \
    --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).