From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, viro@zeniv.linux.org.uk,
arnd@arndb.de, tytso@mit.edu, chur.lee@samsung.com,
cm224.lee@samsung.com, jooyoung.hwang@samsung.com
Subject: Re: [RESEND] Request f2fs filesystem inclusion in linux-next
Date: Mon, 26 Nov 2012 20:37:40 +0900 [thread overview]
Message-ID: <1353929860.26584.63.camel@kjgkr> (raw)
In-Reply-To: <20121126101839.cdea3cebc6534722072e3fd0@canb.auug.org.au>
Hi,
2012-11-26 (월), 10:18 +1100, Stephen Rothwell:
> Hi,
>
> On Sat, 24 Nov 2012 14:28:45 +0900 Jaegeuk Kim <jaegeuk.kim@samsung.com> wrote:
> >
> > About two month ago, I submitted a new file system, namely
> > flash-friendly file system (f2fs) to LKML.
> > http://en.wikipedia.org/wiki/F2FS
> > http://lkml.org/lkml/2012/10/5/205
> > http://lwn.net/Articles/518718/
> >
> > In the mean time, many folks have pointed out several essential issues
> > on f2fs, and now I think most of them have been resolved moderately.
> >
> > So, I'd like to request a new branch being included in linux-next for
> > the purpose of merging into the next mainline kernel.
>
> I have no problem adding this to linux-next (and noone has screamed aver
> the past few days, so that is a good sign) except that the branch you
> have submitted is actually based on linux-next itself. You cannot base
> anything on linux-next as it rebases every day. You need to base your
> tree in Linus' tree (or some other *stable* tree).
>
I've done making a correct tree.
Could you please merge the following f2fs patches?
1. tree
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
2. branch
dev
3. Contact
Jaegeuk Kim <jaegeuk.kim@samsung.com>
4. Short log
Greg Kroah-Hartman (1):
f2fs: move proc files to debugfs
Jaegeuk Kim (16):
f2fs: add document
f2fs: add on-disk layout
f2fs: add superblock and major in-memory structure
f2fs: add super block operations
f2fs: add checkpoint operations
f2fs: add node operations
f2fs: add segment operations
f2fs: add file operations
f2fs: add address space operations for data
f2fs: add core inode operations
f2fs: add inode operations for special inodes
f2fs: add core directory operations
f2fs: add xattr and acl functionalities
f2fs: add garbage collection functions
f2fs: add recovery routines for roll-forward
f2fs: update Kconfig and Makefile
Documentation/filesystems/00-INDEX | 2 +
Documentation/filesystems/f2fs.txt | 417 +++++++++
fs/Kconfig | 1 +
fs/Makefile | 1 +
fs/f2fs/Kconfig | 52 ++
fs/f2fs/Makefile | 7 +
fs/f2fs/acl.c | 465 ++++++++++
fs/f2fs/acl.h | 57 ++
fs/f2fs/checkpoint.c | 792 ++++++++++++++++
fs/f2fs/data.c | 701 ++++++++++++++
fs/f2fs/debug.c | 361 ++++++++
fs/f2fs/dir.c | 672 ++++++++++++++
fs/f2fs/f2fs.h | 1062 +++++++++++++++++++++
fs/f2fs/file.c | 637 +++++++++++++
fs/f2fs/gc.c | 742 +++++++++++++++
fs/f2fs/gc.h | 117 +++
fs/f2fs/hash.c | 98 ++
fs/f2fs/inode.c | 266 ++++++
fs/f2fs/namei.c | 504 ++++++++++
fs/f2fs/node.c | 1763
+++++++++++++++++++++++++++++++++++
fs/f2fs/node.h | 353 +++++++
fs/f2fs/recovery.c | 375 ++++++++
fs/f2fs/segment.c | 1798
++++++++++++++++++++++++++++++++++++
fs/f2fs/segment.h | 615 ++++++++++++
fs/f2fs/super.c | 656 +++++++++++++
fs/f2fs/xattr.c | 389 ++++++++
fs/f2fs/xattr.h | 145 +++
include/linux/f2fs_fs.h | 410 ++++++++
include/uapi/linux/magic.h | 1 +
29 files changed, 13459 insertions(+)
--
Jaegeuk Kim
Samsung
next prev parent reply other threads:[~2012-11-26 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 19:40 [RESEND] Request f2fs filesystem inclusion in linux-next Jaegeuk Kim
2012-11-25 23:18 ` Stephen Rothwell
2012-11-26 11:37 ` Jaegeuk Kim [this message]
2012-11-26 22:48 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2012-11-22 19:41 Jaegeuk Kim
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=1353929860.26584.63.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=chur.lee@samsung.com \
--cc=cm224.lee@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jooyoung.hwang@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).