From: Theodore Ts'o <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] Ext4 changes for 3.14
Date: Tue, 28 Jan 2014 11:27:54 -0500 [thread overview]
Message-ID: <20140128162754.GA17770@thunk.org> (raw)
The following changes since commit d0abafac8c9162f39c4f6b2f8141b772a09b3770:
ext4: fix bigalloc regression (2014-01-06 14:00:23 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus
for you to fetch changes up to d7092ae2973f20a39fee786c47e5edf18ced088f:
ext4: delete "set but not used" variables (2014-01-11 13:26:56 -0500)
----------------------------------------------------------------
Bug fixes and cleanups for ext4. We also enable the punch hole
functionality for bigalloc file systems.
----------------------------------------------------------------
David Howells (1):
ext4: use %pd printk specificer
Jan Kara (2):
ext4: retry allocation when inline->extent conversion failed
ext4: standardize error handling in ext4_da_write_inline_data_begin()
Theodore Ts'o (2):
ext4: avoid clearing beyond i_blocks when truncating an inline data file
ext4: don't pass freed handle to ext4_walk_page_buffers
Yongqiang Yang (2):
ext4: fix a typo in extents.c
ext4: ext4_inode_is_fast_symlink should use EXT4_CLUSTER_SIZE
Zheng Liu (1):
ext4: enable punch hole for bigalloc
jon ernst (1):
ext4: delete "set but not used" variables
fs/ext4/extents.c | 2 +-
fs/ext4/inline.c | 26 +++++++++++++++-----------
fs/ext4/inode.c | 11 +++--------
fs/ext4/ioctl.c | 6 +-----
fs/ext4/namei.c | 5 ++---
5 files changed, 22 insertions(+), 28 deletions(-)
reply other threads:[~2014-01-28 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140128162754.GA17770@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.