From: Jaegeuk Kim <jaegeuk@kernel.org>
To: "HUANG Weller (CM/ESW12-CN)" <Weller.Huang@cn.bosch.com>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: F2FS still EXPERIMENTAL
Date: Tue, 15 Nov 2016 10:38:53 -0800 [thread overview]
Message-ID: <20161115183853.GA45096@jaegeuk> (raw)
In-Reply-To: <7d3b52f7cc84431f81748ccb2de9b4fe@SGPMBX1004.APAC.bosch.com>
On Tue, Nov 15, 2016 at 09:59:25AM +0000, HUANG Weller (CM/ESW12-CN) wrote:
> > Hello,
> >
> > On Tue, Nov 15, 2016 at 05:45:12AM +0000, HUANG Weller (CM/ESW12-CN) wrote:
> > > Hi f2fs developers,
> > >
> > > I am working on the kernel 3.14. I found the F2FS still EXPERIMENTAL.
> > > Could you tell me from which kernel version the f2fs is stable version ?
> >
> > You can pick a backported f2fs from:
> >
> > http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-stable.git
>
> Thanks for your info.
> But I didn't see there is a branch for linux-3.14.y. Does it mean I could not use the f2fs-stable on 3.14 kernel ?
Do you have a chance to change your kernel version?
I've been already maintaining 5 versions actively for android targets, so I'm
not sure I can add one more kernel version for your experiment purpose. I guess
it'd not much difficult to make v3.14 based on v3.18 in f2fs-stable.
Thanks,
>
> Huang Weller
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
------------------------------------------------------------------------------
next prev parent reply other threads:[~2016-11-15 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 5:45 F2FS still EXPERIMENTAL HUANG Weller (CM/ESW12-CN)
2016-11-15 6:29 ` Jaegeuk Kim
2016-11-15 9:59 ` HUANG Weller (CM/ESW12-CN)
2016-11-15 18:38 ` Jaegeuk Kim [this message]
2016-11-16 1:45 ` HUANG Weller (CM/ESW12-CN)
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=20161115183853.GA45096@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=Weller.Huang@cn.bosch.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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