linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Czarcinski <gene@czarc.net>
To: linux-btrfs@vger.kernel.org
Cc: Gene Czarcinski <gene@czarc.net>
Subject: [PATCH 0/4] patches from Fedora 18
Date: Sat, 19 Jan 2013 09:56:21 -0500	[thread overview]
Message-ID: <1358607385-21163-1-git-send-email-gene@czarc.net> (raw)

These are the patches from the Fedora 18 btrfs-progs package.

I claim no authorship and am simply passing these on to the
btrfs mailing list.  There are only four patches.  The 
btrfs-init-dev-list.patch is new to 18.  The others all date
back to at least Fedora 15 in early 2011.

These patches were applied on top of the 19 patches
assembled by David Sterba.  They all applied cleanly
except the valgrind patch where I had to remove a small part
because it had already been fixed by the "plug a memory leak
reported by cppcheck" patch.

Gene Czarcinski (4):
  Fedora 18 - btrfs-init-dev-list.patch
  Fedora 18 - build-fixes.patch
  Fedora 18 - fix-labels.patch
  Fedora 18 - modified valgrind.patch

 btrfsck.c      |  2 ++
 disk-io.c      | 16 +++++++++++-----
 extent-cache.c | 11 +++++++++++
 extent-cache.h |  1 +
 extent-tree.c  | 10 ++++++++++
 mkfs.c         | 11 ++---------
 utils.c        |  3 ++-
 volumes.c      | 16 +++++++++++++++-
 volumes.h      |  1 +
 9 files changed, 55 insertions(+), 16 deletions(-)

-- 
1.8.1


             reply	other threads:[~2013-01-19 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 14:56 Gene Czarcinski [this message]
2013-01-19 14:56 ` [PATCH 1/4] Fedora 18 - btrfs-init-dev-list.patch Gene Czarcinski
2013-01-19 14:56 ` [PATCH 2/4] Fedora 18 - build-fixes.patch Gene Czarcinski
2013-01-19 14:56 ` [PATCH 3/4] Fedora 18 - fix-labels.patch Gene Czarcinski
2013-01-19 14:56 ` [PATCH 4/4] Fedora 18 - modified valgrind.patch Gene Czarcinski

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=1358607385-21163-1-git-send-email-gene@czarc.net \
    --to=gene@czarc.net \
    --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).