From: Chris Mason <chris.mason@oracle.com>
To: Alex Chiang <achiang@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
btrfs-devel@oss.oracle.com
Subject: Re: [ANNOUNCE] Btrfs v0.13
Date: Mon, 31 Mar 2008 16:52:16 -0400 [thread overview]
Message-ID: <200803311652.17234.chris.mason@oracle.com> (raw)
In-Reply-To: <20080331202633.GA341@ldl.fc.hp.com>
On Monday 31 March 2008, Alex Chiang wrote:
> * Chris Mason <chris.mason@oracle.com>:
> > Hello everyone,
> >
> > Btrfs v0.13 is now available for download from:
>
> Hi Chris,
>
> Following are two patches that allow btrfs-progs to build on
> ia64, and prevent a SEGV when trying to do a mkfs.btrfs.
>
> I've gotten as far as successfully creating a btrfs filesystem
> (at least that's what btrfsck tells me), but haven't been able to
> mount it yet, probably because of the sector size issue.
>
Great, thanks I'll take these two. The kernel side needs the same hash.c fix,
but I've already got that change made locally.
-chris
next prev parent reply other threads:[~2008-03-31 20:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 21:09 [ANNOUNCE] Btrfs v0.13 Chris Mason
2008-02-21 21:12 ` Chris Mason
2008-03-31 20:26 ` Alex Chiang
2008-03-31 20:35 ` Alex Chiang
2008-03-31 20:45 ` David Miller
2008-03-31 22:43 ` Alex Chiang
2008-03-31 23:25 ` Alex Chiang
2008-04-01 15:58 ` Chris Mason
2008-03-31 22:47 ` Alex Chiang
2008-04-01 0:40 ` Alex Chiang
2008-04-01 13:38 ` Chris Mason
2008-03-31 20:52 ` Chris Mason [this message]
2008-03-31 21:02 ` Alex Chiang
2008-03-31 20:28 ` [PATCH 1/2] btrfs-progs: Fix printf format casting errors Alex Chiang
2008-03-31 20:29 ` [PATCH 2/2] btrfs-progs: Stop stomping on 'name' input parameter Alex Chiang
2008-04-01 23:28 ` [ANNOUNCE] Btrfs v0.13 Badari Pulavarty
2008-04-01 23:33 ` Badari Pulavarty
2008-04-03 16:51 ` [PATCH] btrfs - replace div_long_long_rem() Badari Pulavarty
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=200803311652.17234.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=achiang@hp.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).