From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PATCH 0/2] Btrfs send fixup
Date: Tue, 25 Feb 2014 19:32:44 +0100 [thread overview]
Message-ID: <cover.1393352970.git.dsterba@suse.cz> (raw)
A fix for the problem that Filipe pointed out and a cleanup in the same code,
depends on the first patch.
Based on btrfs-next/master.
David Sterba (2):
btrfs: send: fix old buffer length in fs_path_ensure_buf
btrfs: send: simplify allocation code in fs_path_ensure_buf
fs/btrfs/send.c | 36 +++++++++++++++---------------------
1 files changed, 15 insertions(+), 21 deletions(-)
--
1.7.9
next reply other threads:[~2014-02-25 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 18:32 David Sterba [this message]
2014-02-25 18:32 ` [PATCH 1/2] btrfs: send: fix old buffer length in fs_path_ensure_buf David Sterba
2014-02-25 18:39 ` Filipe David Manana
2014-02-25 18:33 ` [PATCH 2/2] btrfs: send: simplify allocation code " 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=cover.1393352970.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--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