From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>,
linux-erofs@lists.ozlabs.org, Yue Hu <huyue2@coolpad.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/6] erofs: move zdata.h into zdata.c
Date: Tue, 14 Feb 2023 22:44:53 +0800 [thread overview]
Message-ID: <7af50b7c-cf39-8da0-e73e-2f044a0b1fc7@kernel.org> (raw)
In-Reply-To: <20230204093040.97967-4-hsiangkao@linux.alibaba.com>
On 2023/2/4 17:30, Gao Xiang wrote:
> Definitions in zdata.h are only used in zdata.c and for internal
> use only. No logic changes.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2023-02-14 14:45 UTC|newest]
Thread overview: 32+ 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 ` Gao Xiang
2023-02-04 9:30 ` [PATCH 2/6] erofs: avoid tagged pointers to mark sync decompression Gao Xiang
2023-02-04 9:30 ` Gao Xiang
2023-02-06 1:50 ` Yue Hu
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-04 9:30 ` Gao Xiang
2023-02-06 2:06 ` Yue Hu
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-04 9:30 ` Gao Xiang
2023-02-06 2:14 ` Yue Hu
2023-02-06 2:14 ` Yue Hu
2023-02-14 14:44 ` Chao Yu [this message]
2023-02-04 9:30 ` [PATCH 5/6] erofs: get rid of z_erofs_do_map_blocks() forward declaration Gao Xiang
2023-02-04 9:30 ` Gao Xiang
2023-02-06 1:26 ` Yue Hu
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-04 9:30 ` Gao Xiang
2023-02-06 2:26 ` Yue Hu
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 ` [PATCH 1/6] erofs: get rid of erofs_inode_datablocks() Yue Hu
2023-02-06 1:16 ` Yue Hu
2023-02-07 8:27 ` 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=7af50b7c-cf39-8da0-e73e-2f044a0b1fc7@kernel.org \
--to=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 \
/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.