From: "Mike Audia" <mikey_a@gmx.com>
To: linux-btrfs@vger.kernel.org
Cc: "David Sterba" <dsterba@suse.cz>, sbehrens@giantdisaster.de
Subject: Re: [PATCH v2] btrfs: add mount option to set commit interval
Date: Sat, 03 Aug 2013 07:39:01 -0400 [thread overview]
Message-ID: <20130803113901.157540@gmx.com> (raw)
> > Another newbie question is which version of the kernel do I need to
> > have in order to cleanly apply this patch? I am finding that it fails
> > to apply to the current stable kernel code (as of now it is v3.10.4)
> > which makes me think your patch has to be applied to a newer one? Are
> > you patching against the linux git tree meaning I have to use the 3.11
> > series to try your code?
>
> Try Josef's btrfs-next repo:
>
> https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories#Integration_repository_.28btrfs-next.29
OK! I can patch successfully into that git repo:
% cd /tmp/work
% git clone git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
% cd btrfs
% patch -Np1 -i btrfs_add_mount_option_to_set_commit_interval.patch
patching file fs/btrfs/ctree.h
patching file fs/btrfs/disk-io.c
patching file fs/btrfs/super.c
Hunk #3 succeeded at 647 (offset 19 lines).
Hunk #4 succeeded at 1006 with fuzz 1 (offset 39 lines).
If I am not mistaken, btrfs-next is the entire kernel's code? The wiki suggests running anything compiled therein from the build dir. If I want to compile this into the official 3.10.4 tree, how can I do it?
next reply other threads:[~2013-08-03 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 11:39 Mike Audia [this message]
2013-08-03 11:57 ` [PATCH v2] btrfs: add mount option to set commit interval Hugo Mills
2013-08-05 12:02 ` Mike Audia
-- strict thread matches above, loose matches on Subject: below --
2013-08-02 21:25 Mike Audia
2013-08-02 21:46 ` Zach Brown
2013-08-02 21:12 Mike Audia
2013-08-05 18:33 ` David Sterba
2013-08-01 15:42 [PATCH] " David Sterba
2013-08-01 16:14 ` [PATCH v2] " David Sterba
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=20130803113901.157540@gmx.com \
--to=mikey_a@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.