linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Backporting Recent Btrfs Patches to 2.6.32
Date: Fri, 15 Oct 2010 14:23:00 -0500	[thread overview]
Message-ID: <AANLkTin0HMr2N_hRBu_um+Rf9o+Agjis4E6HLdxkebqv@mail.gmail.com> (raw)

Since the 2.6.32 kernel is one of the long-term stable kernels, and
since a few projects (such as OpenVZ) and distros (such as Debian) are
using the 2.6.32 kernel, I've put together an experimental git branch
to backport later btrfs patches to the 2.6.32 kernel.

Let me know if there's any interest in this experiment, and I'll try
to keep it maintained.

I've placed a git repository containing this work here:

http://gitweb.sabayon.org/?p=linux/kernel/btrfs-backport.git;a=summary

The backport is currently in "works-for-me" status, and I have been
using it for about a week without crashes.

I did not attempt to backport every patch that has touched
linux/fs/btrfs compared to the 2.6.32 kernel.  Some patches were part
of larger kernel updates that would be outside the scope of a
backport.

I was able to backport the DIO patches and the improvements to ENOSPC
handling, as well as most of the other patches in the btrfs-unstable
repository.

Let me know if you have any feedback.

             reply	other threads:[~2010-10-15 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 19:23 Mitch Harder [this message]
2010-11-02 19:36 ` Backporting Recent Btrfs Patches to 2.6.32 Leonidas Spyropoulos

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=AANLkTin0HMr2N_hRBu_um+Rf9o+Agjis4E6HLdxkebqv@mail.gmail.com \
    --to=mitch.harder@sabayonlinux.org \
    --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).