linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "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, 08 Feb 2013 13:16:20 +0900	[thread overview]
Message-ID: <1360296980.8037.5.camel@kjgkr> (raw)
In-Reply-To: <CA+55aFzygotc-rGOBwHmdXU6KrpCE7srqWYs6j-iP5c5Ef3UnA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4624 bytes --]

Ok, I understand.
I'll prepare and send patches for the next merge window with these
patches together.
Thanks,

2013-02-08 (금), 12:09 +1100, Linus Torvalds:
> No.
> 
> You guys need to realize that I'm not talking crap like this this late.
> 
> This is not major bugfixes. I already looked away once just because
> it's a new filesystem, but enough is enough. This is way way WAY too
> late to start sendign "enhancements". Seriously.
> 
> Send them for the next merge window. Not just before rc7.
> 
>                    Linus
> 
> On Thu, Feb 7, 2013 at 11:21 AM, Jaegeuk Kim <jaegeuk.kim@samsung.com> wrote:
> > Hi Linus,
> >
> > Here are four patches which are critical bug fixes on f2fs, three
> > enhancement patches, and a number of trivial patches.
> > Please pull the following tag. Sorry for the late request.
> >
> > Thanks,
> >
> > The following changes since commit
> > 6abb7c25775b7fb2225ad0508236d63ca710e65f:
> >
> >   Merge tag 'regulator-3.8-rc5' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
> > (2013-01-28 22:44:53 -0800)
> >
> > are available in the git repository at:
> >
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
> > tags/f2fs-for-v3.8
> >
> > for you to fetch changes up to 1efc6d3277f59b764384781c0f8dfc821f229380:
> >
> >   f2fs: add compat_ioctl to provide backward compatability (2013-02-06
> > 17:38:59 +0900)
> >
> > ----------------------------------------------------------------
> > f2fs fixes for v3.8
> >
> > [Major bug fixes]
> > o Store device file information correctly
> > o Fix -EIO handling with respect to power-off-recovery
> > o Allocate blocks with global locks
> > o Fix wrong calculation of the SSR cost
> >
> > [Enhancement]
> > o Support (un)freeze_fs
> > o Enhance the f2fs_gc flow
> > o Support 32-bit binary execution on 64-bit kernel
> >
> > ----------------------------------------------------------------
> > Alejandro Martinez Ruiz (1):
> >       f2fs: fix disable_ext_identify option spelling
> >
> > Changman Lee (5):
> >       f2fs: save device node number into f2fs_inode
> >       f2fs: add un/freeze_fs into super_operations
> >       f2fs: stop repeated checking if cp is needed
> >       f2fs: remove repeated F2FS_SET_SB_DIRT call
> >       f2fs: remove unnecessary gc option check and balance_fs
> >
> > Jaegeuk Kim (6):
> >       f2fs: prevent checkpoint once any IO failure is detected
> >       f2fs: cover global locks for reserve_new_block
> >       f2fs: remove the use of page_cache_release
> >       f2fs: avoid balanc_fs during evict_inode
> >       f2fs: clarify and enhance the f2fs_gc flow
> >       f2fs: fix calculation of max. gc cost in the SSR case
> >
> > Namjae Jeon (8):
> >       f2fs: avoid redundant call to has_not_enough_free_secs in f2fs_gc
> >       f2fs: reorganize code for ra_node_page
> >       f2fs: fix typo mistake for data_version description
> >       f2fs: name gc task as per the block device
> >       f2fs: mark gc_thread as NULL when thread creation is failed
> >       f2fs: make an accessor to get sections for particular block type
> >       f2fs: optimize the return condition for has_not_enough_free_secs
> >       f2fs: add compat_ioctl to provide backward compatability
> >
> > majianpeng (4):
> >       f2fs: clean up the add_orphan_inode func
> >       f2fs: add device name in debugfs
> >       f2fs: use F2FS_BLKSIZE to judge bloksize and page_cache_size
> >       f2fs: when check superblock failed, try to check another
> > superblock
> >
> >  fs/f2fs/checkpoint.c |  63 +++++++++++---------------
> >  fs/f2fs/debug.c      |   4 +-
> >  fs/f2fs/f2fs.h       |  32 ++++++++++---
> >  fs/f2fs/file.c       |  35 ++++++++++++---
> >  fs/f2fs/gc.c         | 124
> > ++++++++++++++++++++++-----------------------------
> >  fs/f2fs/gc.h         |  21 ---------
> >  fs/f2fs/inode.c      |  53 +++++++++-------------
> >  fs/f2fs/node.c       |  14 +++---
> >  fs/f2fs/recovery.c   |   4 +-
> >  fs/f2fs/segment.c    |  29 ++++++++----
> >  fs/f2fs/segment.h    |  23 +++-------
> >  fs/f2fs/super.c      |  92 +++++++++++++++++++++++++++++---------
> >  12 files changed, 262 insertions(+), 232 deletions(-)
> >
> > --
> > Jaegeuk Kim
> > Samsung
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Jaegeuk Kim
Samsung

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2013-02-08  4:16 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
2013-02-08 10:54         ` Stephen Rothwell
2013-02-08  4:16   ` Jaegeuk Kim [this message]

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=1360296980.8037.5.camel@kjgkr \
    --to=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 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).