From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: compress: fix to disallow enabling compress on non-empty file
Date: Fri, 25 Sep 2020 16:23:32 -0700 [thread overview]
Message-ID: <20200925232332.GA4136545@google.com> (raw)
In-Reply-To: <d05174f0-4ca6-c492-8ce3-ac8f146e177c@kernel.org>
On 09/26, Chao Yu wrote:
> On 2020-9-26 1:07, Jaegeuk Kim wrote:
> > On 09/25, Chao Yu wrote:
> > > Jaegeuk,
> > >
> > > I noticed that in dev branch there are several patches which have not been
> > > sent to mailing list, could you please send them out?
> >
> > Chao, which patches?
>
> Jaegeuk, they are
>
> f2fs: point man pages for some f2fs utils
Ah, just sent.
> f2fs: fix slab leak of rpages pointer
I did before?
>
> Thanks,
>
> >
> > >
> > > Thanks,
> >
> >
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> >
_______________________________________________
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:[~2020-09-25 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 3:03 [PATCH] f2fs: compress: fix to disallow enabling compress on non-empty file Chao Yu
2020-09-18 3:03 ` [f2fs-dev] " Chao Yu
2020-09-24 20:03 ` Jaegeuk Kim
2020-09-24 20:03 ` [f2fs-dev] " Jaegeuk Kim
2020-09-25 0:57 ` Chao Yu
2020-09-25 0:57 ` [f2fs-dev] " Chao Yu
2020-09-25 9:10 ` Chao Yu
2020-09-25 17:07 ` Jaegeuk Kim
2020-09-25 23:16 ` Chao Yu
2020-09-25 23:23 ` Jaegeuk Kim [this message]
2020-09-25 23:26 ` Jaegeuk Kim
2020-09-25 23:51 ` Chao Yu
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=20200925232332.GA4136545@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.