From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range()
Date: Tue, 7 Feb 2023 20:33:02 +0800 [thread overview]
Message-ID: <ca2d2f96-b951-84b6-171f-683a4c7c68da@kernel.org> (raw)
In-Reply-To: <Y+B21EAHfuw2vyJ6@google.com>
On 2023/2/6 11:41, Jaegeuk Kim wrote:
> On 02/01, Chao Yu wrote:
>> On 2023/2/1 2:56, Jaegeuk Kim wrote:
>>> I wanted to avoid a deep if/else statement.
>>
>> So how about this:
>
> Nothing impressive.
Oops...
Thanks,
_______________________________________________
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:[~2023-02-07 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:46 [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range() Chao Yu
2023-01-31 14:47 ` [f2fs-dev] [PATCH 2/3] f2fs: fix to update age extent correctly during truncation Chao Yu
2023-01-31 14:47 ` [f2fs-dev] [PATCH 3/3] f2fs: fix to update age extent in f2fs_do_zero_range() Chao Yu
2023-01-31 18:56 ` [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range() Jaegeuk Kim
2023-02-01 8:53 ` Chao Yu
2023-02-06 3:41 ` Jaegeuk Kim
2023-02-07 12:33 ` Chao Yu [this message]
2023-01-31 19:10 ` patchwork-bot+f2fs
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=ca2d2f96-b951-84b6-171f-683a4c7c68da@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).