On Wed, Feb 06, 2013 at 06:03:14AM -0700, Marguerite Su wrote: > On Wed, Feb 6, 2013 at 4:45 AM, Josef Bacik <jba...@fusionio.com> wrote: > > Ok so I think we've fixed this already, can you build btrfs-next and try > > mounting with that and see if it fixes the problem? Thanks, > > Hi, Josef, > > Is there any btrfs git compatible with kernel 3.7 and absorbs this > fix? So I can dkms it, I'm using openSUSE 12.3 Beta1 with kernel 3.7, > I can update to 3.8, but next time I do system update to RC1 it will > fallback to 3.7 again. > > #btrfs-next seems to move forward to 3.8. /uapi/linux/btrfs.h doesn't > exist in kernel 3.7, it still use the old ioctl.h, I tried to revert > the ioctl.h > btrfs.h patch, but there's still errors about: > > /usr/src/linux-3.7.1-1/include/trace/events/btrfs.h: In function > ‘ftrace_raw_event_btrfs_transaction_commit’: > /usr/src/linux-3.7.1-1/include/trace/events/btrfs.h:61:1: error: > incompatible types when assigning to type ‘u64’ from type ‘atomic64_t’ >
Btrfs-next is based on 3.7, you should be able to just git diff v3.7.. > whatever.patch and get all the changes you need. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
