From: amir73il@users.sourceforge.net
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: [PATCH 0/4] ext4: reduce the size of inode.c
Date: Tue, 21 Jun 2011 12:39:24 +0300 [thread overview]
Message-ID: <1308649168-12543-1-git-send-email-amir73il@users.sourceforge.net> (raw)
inode.c has grown to almost 6000 lines and contains code for a wide variety
of functionalities.
This patch series reduces the file's size to under 4500 lines, by moving all
indirect inode specific implementations to a new file called indirect.c.
This convention is aligned with extent inode code being mostly in extents.c.
My own ulterior motive is that the snapshot patches were about to add another
~500 lines to inode.c, so now most of those lines will be added to indirect.c.
[PATCH 1/4] ext4: split ext4_ind_truncate from ext4_truncate
[PATCH 2/4] ext4: rename ext4_indirect_* funcs to ext4_ind_*
[PATCH 3/4] ext4: clone indirect.c file from inode.c
[PATCH 4/4] ext4: move ext4_ind_* functions from inode.c to indirect.c
next reply other threads:[~2011-06-21 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 9:39 amir73il [this message]
2011-06-21 9:39 ` [PATCH 1/4] ext4: split ext4_ind_truncate from ext4_truncate amir73il
2011-06-21 9:39 ` [PATCH 2/4] ext4: rename ext4_indirect_* funcs to ext4_ind_* amir73il
2011-06-21 9:39 ` [PATCH 3/4] ext4: clone indirect.c file from inode.c amir73il
2011-06-27 23:41 ` Ted Ts'o
2011-06-27 23:44 ` [PATCH 1/3] ext4: move __ext4_check_blockref to block_validity.c Theodore Ts'o
2011-06-27 23:44 ` [PATCH 2/3] ext4: move common truncate functions to header file Theodore Ts'o
2011-06-27 23:44 ` [PATCH 3/3] ext4: move ext4_ind_* functions from inode.c to indirect.c Theodore Ts'o
2011-06-28 7:02 ` [PATCH 3/4] ext4: clone indirect.c file from inode.c Amir G.
2011-06-21 9:39 ` [PATCH 4/4] ext4: move ext4_ind_* functions from inode.c to indirect.c amir73il
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=1308649168-12543-1-git-send-email-amir73il@users.sourceforge.net \
--to=amir73il@users.sourceforge.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).