From: Baokun Li via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: <linux-erofs@lists.ozlabs.org>
Cc: brauner@kernel.org, yangerkun@huawei.com,
linux-kernel@vger.kernel.org, huyue2@coolpad.com,
viro@zeniv.linux.org.uk
Subject: [PATCH -next v3 0/2] erofs: reliably distinguish block based and fscache mode
Date: Fri, 19 Apr 2024 20:36:09 +0800 [thread overview]
Message-ID: <20240419123611.947084-1-libaokun1@huawei.com> (raw)
Hi Christian,
As your original patch had some "DOS line endings", I failed at am it, so
manually changed the relevant content when making v2, which caused Author
to be modified, I just noticed this and corrected it, apologies for that.
Changes since v2:
Get rid of erofs_fs_context.
Changes since v1:
Allocate and initialise fc->s_fs_info in erofs_fc_get_tree() instead of
modifying fc->sb_flags.
V1: https://lore.kernel.org/r/20240415121746.1207242-1-libaokun1@huawei.com/
V2: https://lore.kernel.org/r/20240417065513.3409744-1-libaokun1@huawei.com/
Baokun Li (1):
erofs: get rid of erofs_fs_context
Christian Brauner (1):
erofs: reliably distinguish block based and fscache mode
fs/erofs/internal.h | 7 ---
fs/erofs/super.c | 124 ++++++++++++++++++++------------------------
2 files changed, 55 insertions(+), 76 deletions(-)
--
2.31.1
next reply other threads:[~2024-04-19 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 12:36 Baokun Li via Linux-erofs [this message]
2024-04-19 12:36 ` [PATCH -next v3 1/2] erofs: get rid of erofs_fs_context Baokun Li via Linux-erofs
2024-04-22 10:25 ` Jingbo Xu
2024-04-22 11:31 ` Baokun Li via Linux-erofs
2024-04-22 11:39 ` Jingbo Xu
2024-04-23 10:37 ` Gao Xiang
2024-04-28 7:10 ` Gao Xiang
2024-04-28 10:00 ` Chao Yu
2024-04-19 12:36 ` [PATCH -next v3 2/2] erofs: reliably distinguish block based and fscache mode Baokun Li via Linux-erofs
2024-04-22 11:52 ` Jingbo Xu
2024-04-28 7:17 ` Gao Xiang
2024-04-28 10:03 ` 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=20240419123611.947084-1-libaokun1@huawei.com \
--to=linux-erofs@lists.ozlabs.org \
--cc=brauner@kernel.org \
--cc=huyue2@coolpad.com \
--cc=libaokun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yangerkun@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).