From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2 v2] f2fs: attach IO flags to the missing cases
Date: Mon, 8 Jun 2020 05:58:55 -0700 [thread overview]
Message-ID: <20200608125855.GA200855@google.com> (raw)
In-Reply-To: <70f2b6f6-189f-bafe-6db8-7c16a4a7f6ac@huawei.com>
On 06/08, Chao Yu wrote:
> Jaegeuk,
>
> This patch should be applied before "f2fs: attach IO flags to the missing cases",
> otherwise, gcc may complain about implicit declaration of "__attach_io_flag".
Yup. Done. :P
>
> On 2020/6/8 10:51, Jaegeuk Kim wrote:
> > This patch adds another way to attach bio flags to node writes.
> >
> > Description: Give a way to attach REQ_META|FUA to node writes
> > given temperature-based bits. Now the bits indicate:
> > * REQ_META | REQ_FUA |
> > * 5 | 4 | 3 | 2 | 1 | 0 |
> > * Cold | Warm | Hot | Cold | Warm | Hot |
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH 2/2 v2] f2fs: attach IO flags to the missing cases
Date: Mon, 8 Jun 2020 05:58:55 -0700 [thread overview]
Message-ID: <20200608125855.GA200855@google.com> (raw)
In-Reply-To: <70f2b6f6-189f-bafe-6db8-7c16a4a7f6ac@huawei.com>
On 06/08, Chao Yu wrote:
> Jaegeuk,
>
> This patch should be applied before "f2fs: attach IO flags to the missing cases",
> otherwise, gcc may complain about implicit declaration of "__attach_io_flag".
Yup. Done. :P
>
> On 2020/6/8 10:51, Jaegeuk Kim wrote:
> > This patch adds another way to attach bio flags to node writes.
> >
> > Description: Give a way to attach REQ_META|FUA to node writes
> > given temperature-based bits. Now the bits indicate:
> > * REQ_META | REQ_FUA |
> > * 5 | 4 | 3 | 2 | 1 | 0 |
> > * Cold | Warm | Hot | Cold | Warm | Hot |
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> Thanks,
next prev parent reply other threads:[~2020-06-08 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 23:50 [f2fs-dev] [PATCH 1/2] f2fs: add node_io_flag for bio flags likewise data_io_flag Jaegeuk Kim
2020-06-04 23:50 ` Jaegeuk Kim
2020-06-04 23:50 ` [f2fs-dev] [PATCH 2/2] f2fs: attach IO flags to the missing cases Jaegeuk Kim
2020-06-04 23:50 ` Jaegeuk Kim
2020-06-08 2:18 ` [f2fs-dev] " Chao Yu
2020-06-08 2:18 ` Chao Yu
2020-06-08 2:51 ` [f2fs-dev] [PATCH 2/2 v2] " Jaegeuk Kim
2020-06-08 2:51 ` Jaegeuk Kim
2020-06-08 8:35 ` [f2fs-dev] " Chao Yu
2020-06-08 8:35 ` Chao Yu
2020-06-08 12:58 ` Jaegeuk Kim [this message]
2020-06-08 12:58 ` Jaegeuk Kim
2020-06-08 2:18 ` [f2fs-dev] [PATCH 1/2] f2fs: add node_io_flag for bio flags likewise data_io_flag Chao Yu
2020-06-08 2:18 ` 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=20200608125855.GA200855@google.com \
--to=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.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 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.