From: Yiyang Wu <toolmanp@tlmp.cc>
To: hsiangkao@linux.alibaba.com
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH V4 0/2] erofs: refactor fast_symlink and read_inode
Date: Mon, 2 Sep 2024 16:31:45 +0800 [thread overview]
Message-ID: <20240902083147.450558-1-toolmanp@tlmp.cc> (raw)
This patchset is response to the original suggestions posted here[1].
Since my later work is somehow related to this issue, i think it's
better to deal with it first.
Changes in V2:
1. Lift the erofs_fill_symlink patch to 1/2
2. Fix code styles problems in read_inode patch.
3. Fix the formatting problems caused by clang-format.
Changes in V3:
1. Remove some redundant variables and statements in both patches.
Changes in V4:
1. Remove out_unlock in erofs_fill_inode and use early returns.
2. Fix missing initializer for erofs_buf in erofs_read_inode.
[1]: https://lore.kernel.org/all/20240425222847.GN2118490@ZenIV/
Yiyang Wu (2):
erofs: use kmemdup_nul in erofs_fill_symlink
erofs: refactor read_inode calling convention
fs/erofs/inode.c | 133 ++++++++++++++++++++++-------------------------
1 file changed, 61 insertions(+), 72 deletions(-)
--
2.46.0
next reply other threads:[~2024-09-02 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 8:31 Yiyang Wu [this message]
2024-09-02 8:31 ` [PATCH V4 1/2] erofs: use kmemdup_nul in erofs_fill_symlink Yiyang Wu
2024-09-02 8:52 ` Gao Xiang
2024-09-02 9:04 ` Gao Xiang
2024-09-09 3:37 ` Chao Yu
2024-09-02 8:31 ` [PATCH V4 2/2] erofs: refactor read_inode calling convention Yiyang Wu
[not found] ` <ca8dea24-1ef2-46a8-bfca-72aeffa1f6e6@linux.alibaba.com>
2024-09-02 9:34 ` Yiyang Wu
2024-09-02 9:54 ` Gao Xiang
2024-09-03 2:37 ` Gao Xiang
2024-09-09 3:41 ` Chao Yu
2024-09-02 9:36 ` Yiyang Wu
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=20240902083147.450558-1-toolmanp@tlmp.cc \
--to=toolmanp@tlmp.cc \
--cc=hsiangkao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome