From: lihong <koulihong@huawei.com>
To: <yuchao0@huawei.com>, <jaegeuk@kernel.org>
Cc: zengguangyue@hisilicon.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/2] add a new fio cache for IPU.
Date: Wed, 16 Oct 2019 17:33:20 +0800 [thread overview]
Message-ID: <9e93eae3-18f6-43d7-889d-f22568428bf8@huawei.com> (raw)
In-Reply-To: <1571217722-88090-1-git-send-email-koulihong@huawei.com>
Please ignore this patch, there are some format errors in the commit
description, i will send the patchs with
the fix.
在 2019/10/16 17:22, Lihong Kou 写道:
> *** BLURB HERE ***
>
> Lihong Kou (1):
> Revert "f2fs: add bio cache for IPU"
>
> k00417925 (1):
> f2fs: introduce a new fio cache for IPU.
>
> fs/f2fs/checkpoint.c | 1 +
> fs/f2fs/data.c | 93 ++++++++--------------------------------------------
> fs/f2fs/f2fs.h | 4 +--
> fs/f2fs/segment.c | 22 ++++++-------
> fs/f2fs/super.c | 2 ++
> 5 files changed, 29 insertions(+), 93 deletions(-)
>
_______________________________________________
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:[~2019-10-16 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 9:22 [f2fs-dev] [PATCH 0/2] add a new fio cache for IPU Lihong Kou
2019-10-16 9:22 ` [f2fs-dev] [PATCH 1/2] Revert "f2fs: add bio cache for IPU" Lihong Kou
2019-10-16 9:22 ` [f2fs-dev] [PATCH 2/2] f2fs: introduce a new fio cache for IPU Lihong Kou
2019-10-16 9:33 ` lihong [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-16 9:15 [f2fs-dev] [PATCH 0/2] add " Lihong Kou
2019-10-16 9:33 ` lihong
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=9e93eae3-18f6-43d7-889d-f22568428bf8@huawei.com \
--to=koulihong@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
--cc=zengguangyue@hisilicon.com \
/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).