From: Chris Mason <chris.mason@oracle.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-btrfs@vger.kernel.org, davem@davemloft.net, a.beregalov@gmail.com
Subject: Re: WARNING at fs/btrfs/extent_io.c:3618 write_extent_buffer (sparc64)
Date: Fri, 5 Feb 2010 10:20:11 -0500 [thread overview]
Message-ID: <20100205152011.GA2858@think> (raw)
In-Reply-To: <alpine.DEB.2.01.1002050233390.3483@bogon.housecafe.de>
On Fri, Feb 05, 2010 at 02:43:01AM -0800, Christian Kujau wrote:
> When mounting a newly created btrfs on sparc64, the following warning is
> printed (vanilla 2.6.33-rc6, Feb 03):
Ok, I've got a sparc box on the way, and I'll cleanup these errors.
-chris
prev parent reply other threads:[~2010-02-05 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 10:43 WARNING at fs/btrfs/extent_io.c:3618 write_extent_buffer (sparc64) Christian Kujau
2010-02-05 15:20 ` Chris Mason [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=20100205152011.GA2858@think \
--to=chris.mason@oracle.com \
--cc=a.beregalov@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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