From: Yangtao Li via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com,
jefflexu@linux.alibaba.com, tytso@mit.edu,
adilger.kernel@dilger.ca, rpeterso@redhat.com,
agruenba@redhat.com, mark@fasheh.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, viro@zeniv.linux.org.uk,
brauner@kernel.org
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-erofs@lists.ozlabs.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v4 2/5] erofs: convert to use i_blockmask()
Date: Fri, 10 Mar 2023 14:15:49 +0800 [thread overview]
Message-ID: <20230310061549.11254-1-frank.li@vivo.com> (raw)
In-Reply-To: <e8054874-88d8-e539-8fd4-6123821aa3a8@linux.alibaba.com>
Hi Gao Xiang,
> Please help drop this one since we'd like to use it until i_blockmask() lands to upstream.
I'm OK. Not sure if I need to resend v5?
Thx,
Yangtao
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2023-03-22 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 5:48 [Ocfs2-devel] [PATCH v4 1/5] fs: add i_blockmask() Yangtao Li via Ocfs2-devel
2023-03-10 5:48 ` [Ocfs2-devel] [PATCH v4 2/5] erofs: convert to use i_blockmask() Yangtao Li via Ocfs2-devel
2023-03-10 6:01 ` Gao Xiang via Ocfs2-devel
2023-03-10 6:15 ` Yangtao Li via Ocfs2-devel [this message]
2023-03-10 6:20 ` Gao Xiang via Ocfs2-devel
2023-03-10 5:48 ` [Ocfs2-devel] [PATCH v4 3/5] gfs2: " Yangtao Li via Ocfs2-devel
2023-03-10 5:48 ` [Ocfs2-devel] [PATCH v4 4/5] ocfs2: " Yangtao Li via Ocfs2-devel
2023-03-10 11:13 ` Joseph Qi via Ocfs2-devel
2023-03-10 5:48 ` [Ocfs2-devel] [PATCH v4 5/5] fs/remap_range: " Yangtao Li via Ocfs2-devel
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=20230310061549.11254-1-frank.li@vivo.com \
--to=ocfs2-devel@oss.oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=agruenba@redhat.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=cluster-devel@redhat.com \
--cc=frank.li@vivo.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=rpeterso@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xiang@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;
as well as URLs for NNTP newsgroup(s).