From: Chao Yu <chao@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Peter Collingbourne <pcc@google.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] Fix the struct f2fs_dentry_block size check
Date: Sun, 19 Jun 2022 07:41:28 +0800 [thread overview]
Message-ID: <0bf9bc18-99a9-e0a0-bb4c-dc398361c23d@kernel.org> (raw)
In-Reply-To: <20220614231724.776264-2-bvanassche@acm.org>
On 2022/6/15 7:17, Bart Van Assche wrote:
> Fix the f2fs-tools build on systems for which PAGE_SIZE != 4096.
>
> Cc: Peter Collingbourne <pcc@google.com>
> Reported-by: Peter Collingbourne <pcc@google.com>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-06-18 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 23:17 [f2fs-dev] [PATCH 0/3] Three f2fs patches Bart Van Assche
2022-06-14 23:17 ` [f2fs-dev] [PATCH 1/3] Fix the struct f2fs_dentry_block size check Bart Van Assche
2022-06-18 23:41 ` Chao Yu [this message]
[not found] ` <CAMn1gO4=iy7tzvvcx6n5DLBM+V4f9Kj=_U1abRf4Cm8XAL+gCA@mail.gmail.com>
2022-06-19 22:12 ` Jaegeuk Kim
2022-06-14 23:17 ` [f2fs-dev] [PATCH 2/3] Fix f2fs_report_zone() Bart Van Assche
2022-06-18 23:41 ` Chao Yu
2022-06-14 23:17 ` [f2fs-dev] [PATCH 3/3] Improve compile-time type checking for f2fs_report_zone() Bart Van Assche
2022-06-18 23:42 ` Chao Yu
2022-06-15 16:58 ` [f2fs-dev] [PATCH 0/3] Three f2fs patches Jaegeuk Kim
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=0bf9bc18-99a9-e0a0-bb4c-dc398361c23d@kernel.org \
--to=chao@kernel.org \
--cc=bvanassche@acm.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=pcc@google.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 NNTP newsgroup(s).