From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: [PULL REQUEST] UDF fixes for 2.6.32-rc1
Date: Mon, 14 Sep 2009 19:52:28 +0200 [thread overview]
Message-ID: <20090914175228.GF25549@duck.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git for_linus
to get:
Jan Kara (4):
udf: Remove dead code
udf: Remove wrong assignment in udf_symlink
udf: Perform preallocation only for regular files
udf: Fix possible corruption when close races with write
The diffstat is
fs/udf/directory.c | 86 ----------------------------------------------------
fs/udf/file.c | 2 +
fs/udf/inode.c | 19 ++++++-----
fs/udf/lowlevel.c | 4 --
fs/udf/namei.c | 1 -
5 files changed, 12 insertions(+), 100 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
reply other threads:[~2009-09-14 17:52 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=20090914175228.GF25549@duck.suse.cz \
--to=jack@suse.cz \
--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).