From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] sload.f2fs: use F2FS_COMPRESS_RELEASED instead of IMMUTABLE bit
Date: Thu, 10 Jun 2021 09:51:00 -0700 [thread overview]
Message-ID: <YMJC9CY2nCG/6mp5@google.com> (raw)
In-Reply-To: <fec816fb-a4c9-0e65-5f09-8c9fdae73c87@kernel.org>
On 06/10, Chao Yu wrote:
> On 2021/6/10 2:42, Jaegeuk Kim wrote:
> > On 06/08, Chao Yu wrote:
> > > On 2021/6/8 0:52, Jaegeuk Kim wrote:
> > > > On 06/06, Chao Yu wrote:
> > > > > On 2021/5/26 4:51, Jaegeuk Kim wrote:
> > > > > > Let's use F2FS_COMPRESS_RELEASED to disallow writes only.
> > > > > >
> > > > > > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > > > >
> > > > > Reviewed-by: Chao Yu <yuchao0@huawei.com>
> > > >
> > > > Too late, as I published it in master.
> > >
> > > Oops, sorry for the delay.
> > >
> > > So does the patch "f2fs-tools: support small RO partition"?
> >
> > sload.f2fs: use F2FS_COMPRESS_RELEASED instead of IMMUTABLE bit
>
> Oh, I mean does patch "f2fs-tools: support small RO partition" be
> pushed as well? if so, seems I don't need to reply with the
> reviewed-by flag.
Yes, it was merged in aosp.
>
> Thanks,
>
> >
> > >
> > > Thanks,
> > >
> > > >
> > > > >
> > > > > Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-06-10 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 20:51 [f2fs-dev] [PATCH] sload.f2fs: use F2FS_COMPRESS_RELEASED instead of IMMUTABLE bit Jaegeuk Kim
2021-06-06 13:54 ` Chao Yu
2021-06-07 16:52 ` Jaegeuk Kim
2021-06-07 23:10 ` Chao Yu
2021-06-09 18:42 ` Jaegeuk Kim
2021-06-10 15:00 ` Chao Yu
2021-06-10 16:51 ` 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=YMJC9CY2nCG/6mp5@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--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 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.