From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Linux F2FS DEV,
Mailing List" <linux-f2fs-devel@lists.sourceforge.net>,
"Linux Kernel, Mailing List" <linux-kernel@vger.kernel.org>,
"Linux FS DEV, Mailing List" <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] f2fs fixes for v3.8-rc7
Date: Fri, 8 Feb 2013 08:01:48 +0000 [thread overview]
Message-ID: <20130208080148.GG4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1360297231.8037.8.camel@kjgkr>
On Fri, Feb 08, 2013 at 01:20:31PM +0900, Jaegeuk Kim wrote:
> Hi Al,
>
> Could you send the patches to me?
> I'll merge them in my tree and submit them in the next merge window.
> Is it OK?
Feel free to fetch/cherry-pick or simply pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git f2fs
- that branchlet grows directly off the mainline and it's not going to
be rebased...
Shortlog:
Al Viro (4):
f2fs: init_dent_inode() should take qstr
f2fs: switch new_inode_page() from dentry to qstr
f2fs: switch init_inode_metadata() to passing parent and name separately
f2fs: get rid of fake on-stack dentries
Diffstat:
fs/f2fs/dir.c | 29 +++++++++++++----------------
fs/f2fs/f2fs.h | 12 +++++++++---
fs/f2fs/node.c | 4 ++--
fs/f2fs/recovery.c | 12 +++++-------
4 files changed, 29 insertions(+), 28 deletions(-)
next prev parent reply other threads:[~2013-02-08 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 0:21 [GIT PULL] f2fs fixes for v3.8-rc7 Jaegeuk Kim
2013-02-08 1:09 ` Linus Torvalds
2013-02-08 3:10 ` Al Viro
2013-02-08 4:20 ` Jaegeuk Kim
2013-02-08 8:01 ` Al Viro [this message]
2013-02-08 10:54 ` Stephen Rothwell
2013-02-08 4:16 ` 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=20130208080148.GG4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.