From: Jan Kara <jack@suse.cz>
To: marcin.slusarz@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] udf: next round of cleanups
Date: Mon, 4 Feb 2008 20:37:14 +0100 [thread overview]
Message-ID: <20080204193714.GO3426@duck.suse.cz> (raw)
In-Reply-To: <1202063631-18145-1-git-send-email-marcin.slusarz@gmail.com>
On Sun 03-02-08 19:33:45, marcin.slusarz@gmail.com wrote:
> Hi
>
> This patchset contains next round of various UDF fs cleanups.
>
> [PATCH 1/6] udf: udf_get_block, inode_bmap - remove unneeded checks
>
> [PATCH 2/6] udf: create function for conversion from timestamp to timespec
> [PATCH 3/6] udf: convert udf_stamp_to_time to return struct timespec
> [PATCH 4/6] udf: convert udf_stamp_to_time and udf_time_to_stamp to use timestamps
> [PATCH 5/6] udf: remove unneeded kernel_timestamp type
> These 4 patches can be folded into one if requested, but I think it's
> easier to analyze them when they are split.
>
> [PATCH 6/6] udf: super.c reorganization
> Pretty mechanical work. Can be dropped and redone if it will
> conflict with someone else patch.
>
> fs/udf/ecma_167.h | 13 -
> fs/udf/inode.c | 183 ++++++-----------
> fs/udf/super.c | 553 ++++++++++++++++++++++++++----------------------------
> fs/udf/udfdecl.h | 8
> fs/udf/udfend.h | 22 --
> fs/udf/udftime.c | 39 +--
> 6 files changed, 358 insertions(+), 460 deletions(-)
>
> Applies on top of patches I've sent lately (http://lkml.org/lkml/2008/1/30/482)
>
> Jan: Are you going to create git tree for udf?
I was already thinking about it to take some burden from Andrew. So if
you think you are going to have more time for these cleanups then I can
setup one (it would be useless when I send to Andrew one fix per month ;)...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2008-02-04 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 18:33 marcin.slusarz
2008-02-04 19:37 ` Jan Kara [this message]
2008-02-03 18:36 marcin.slusarz
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=20080204193714.GO3426@duck.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
/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
all inboxes | Powered by JetHome®