From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org, Chao Yu <chao@kernel.org>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
LKML <linux-kernel@vger.kernel.org>,
huyue2@coolpad.com, zhangwen@coolpad.com
Subject: Re: [PATCH 1/6] erofs: get rid of erofs_inode_datablocks()
Date: Mon, 6 Feb 2023 09:16:25 +0800 [thread overview]
Message-ID: <20230206091625.00000a70.zbestahu@gmail.com> (raw)
In-Reply-To: <20230204093040.97967-1-hsiangkao@linux.alibaba.com>
On Sat, 4 Feb 2023 17:30:35 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
> erofs_inode_datablocks() has the only one caller, let's just get
> rid of it entirely. No logic changes.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Yue Hu <huyue2@coolpad.com>
next prev parent reply other threads:[~2023-02-06 1:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 9:30 [PATCH 1/6] erofs: get rid of erofs_inode_datablocks() Gao Xiang
2023-02-04 9:30 ` [PATCH 2/6] erofs: avoid tagged pointers to mark sync decompression Gao Xiang
2023-02-06 1:50 ` Yue Hu
2023-02-14 14:42 ` Chao Yu
2023-02-04 9:30 ` [PATCH 3/6] erofs: remove tagged pointer helpers Gao Xiang
2023-02-06 2:06 ` Yue Hu
2023-02-14 14:44 ` Chao Yu
2023-02-04 9:30 ` [PATCH 4/6] erofs: move zdata.h into zdata.c Gao Xiang
2023-02-06 2:14 ` Yue Hu
2023-02-14 14:44 ` Chao Yu
2023-02-04 9:30 ` [PATCH 5/6] erofs: get rid of z_erofs_do_map_blocks() forward declaration Gao Xiang
2023-02-06 1:26 ` Yue Hu
2023-02-14 14:45 ` Chao Yu
2023-02-04 9:30 ` [PATCH 6/6] erofs: tidy up internal.h Gao Xiang
2023-02-06 2:26 ` Yue Hu
2023-02-07 8:48 ` Jingbo Xu
2023-02-14 14:46 ` Chao Yu
2023-02-06 1:16 ` Yue Hu [this message]
2023-02-07 8:27 ` [PATCH 1/6] erofs: get rid of erofs_inode_datablocks() Jingbo Xu
2023-02-14 13:45 ` 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=20230206091625.00000a70.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangwen@coolpad.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