From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org, LMKL <linux-kernel@vger.kernel.org>,
huyue2@coolpad.com
Subject: Re: [PATCH v2] erofs: tidy up EROFS on-disk naming
Date: Fri, 31 Mar 2023 14:59:28 +0800 [thread overview]
Message-ID: <20230331145928.00002cc0.zbestahu@gmail.com> (raw)
In-Reply-To: <20230331063149.25611-1-hsiangkao@linux.alibaba.com>
On Fri, 31 Mar 2023 14:31:49 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
> - Get rid of all "vle" (variable-length extents) expressions
> since they only expand overall name lengths unnecessarily;
> - Rename COMPRESSION_LEGACY to COMPRESSED_FULL;
> - Move on-disk directory definitions ahead of compression;
> - Drop unused extended attribute definitions;
> - Move inode ondisk union `i_u` out as `union erofs_inode_i_u`.
>
> No actual logical change.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Yue Hu <huyue2@coolpad.com>
next prev parent reply other threads:[~2023-03-31 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 5:49 [PATCH] erofs: tidy up EROFS on-disk naming Gao Xiang
2023-03-29 6:37 ` Yue Hu
2023-03-31 6:31 ` [PATCH v2] " Gao Xiang
2023-03-31 6:59 ` Yue Hu [this message]
2023-04-16 14:15 ` 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=20230331145928.00002cc0.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@coolpad.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox