From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: Josef Bacik <josef@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs-progs: add support for mixed data+metadata block groups V3
Date: Sat, 6 Nov 2010 16:10:54 -0500 [thread overview]
Message-ID: <AANLkTikC+JFSGeb585oO2AdMSBtFqgSPXbHoePmPtDvC@mail.gmail.com> (raw)
In-Reply-To: <20101029010308.GC11684@dhcp231-156.rdu.redhat.com>
My apologies if I missed it, but this looks like the most recent
version of this patch ([PATCH] Btrfs-progs: add support for mixed
data+metadata block groups V3), and this version needs updating to
take into account that BTRFS_FEATURE_INCOMPAT_SPACE_CACHE is no longer
needed.
The kernel btrfs code expects:
#define BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS (1ULL << 2)
But this version of the patch gives:
#define BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS (1ULL << 3)
with (1ULL << 2) being occupied by the space_cache incompat flag.
prev parent reply other threads:[~2010-11-06 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 18:37 [PATCH] Btrfs-progs: add support for mixed data+metadata block groups V3 Josef Bacik
2010-10-29 0:20 ` Cláudio Martins
2010-10-29 1:03 ` Josef Bacik
2010-11-06 21:10 ` Mitch Harder [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=AANLkTikC+JFSGeb585oO2AdMSBtFqgSPXbHoePmPtDvC@mail.gmail.com \
--to=mitch.harder@sabayonlinux.org \
--cc=josef@redhat.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;
as well as URLs for NNTP newsgroup(s).