From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com, David Sterba <dsterba@suse.cz>
Subject: [PULL] [PATCH 0/2] Minor fixups from 3.16-rc1
Date: Fri, 20 Jun 2014 12:07:05 +0200 [thread overview]
Message-ID: <cover.1403258476.git.dsterba@suse.cz> (raw)
Hi Chris,
two minor fixups for patches merged in rc1
You can also pull that from
git://repo.or.cz/linux-2.6/btrfs-unstable.git for-chris/3.16-rc2
with top commit b934864cc8b08eb358748b06468b9cca64026c1e,
based on current for-linus 8408c716d7a4ddd5954ce33f53a7d3cd2876cf65
Thanks.
David Sterba (2):
btrfs: remove stale comment from btrfs_flush_all_pending_stuffs
btrfs: use E2BIG instead of EIO if compression does not help
fs/btrfs/transaction.c | 5 -----
fs/btrfs/zlib.c | 2 +-
2 files changed, 1 insertions(+), 6 deletions(-)
--
1.7.9
next reply other threads:[~2014-06-20 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 10:07 David Sterba [this message]
2014-06-20 10:07 ` [PATCH 1/2] btrfs: remove stale comment from btrfs_flush_all_pending_stuffs David Sterba
2014-06-20 10:07 ` [PATCH 2/2] btrfs: use E2BIG instead of EIO if compression does not help 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.1403258476.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--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).