From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] ext3, udf, quota fixes
Date: Mon, 17 Dec 2012 15:33:26 +0100 [thread overview]
Message-ID: <20121217143326.GA2669@quack.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
to get some ext3 & quota cleanups and couple of udf fixes.
Top of the tree is 56df127. The full shortlog is:
Julia Lawall (1):
ext3: drop if around WARN_ON
Lee Jones (1):
quota: Use the pre-processor to compile out quotactl_cmd_write when !CONFIG_BLOCK
Namjae Jeon (3):
udf: fix memory leak while allocating blocks during write
udf: don't increment lenExtents while writing to a hole
udf: remove un-needed variable from inode_getblk
Zhao Hongjiang (1):
ext3: get rid of the duplicate code on ext3_fill_super
The diffstat is
fs/ext3/inode.c | 3 +--
fs/ext3/super.c | 3 ---
fs/quota/quota.c | 4 ++++
fs/udf/inode.c | 14 +++++++++-----
4 files changed, 14 insertions(+), 10 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
reply other threads:[~2012-12-17 14:33 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=20121217143326.GA2669@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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 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).