From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/3] Three f2fs patches
Date: Wed, 15 Jun 2022 09:58:02 -0700 [thread overview]
Message-ID: <YqoPmgP5DbkXpMmh@google.com> (raw)
In-Reply-To: <20220614231724.776264-1-bvanassche@acm.org>
Thanks, merged.
On 06/14, Bart Van Assche wrote:
> Hi Jaegeuk,
>
> This patch series fixes one issue reported by Peter Collingbourne and two
> issues I discovered by reading the zoned block device source code. Please
> consider these patches for inclusion in the official f2fs-tools repository.
>
> Thanks,
>
> Bart.
>
> Bart Van Assche (3):
> Fix the struct f2fs_dentry_block size check
> Fix f2fs_report_zone()
> Improve compile-time type checking for f2fs_report_zone()
>
> include/f2fs_fs.h | 6 ++++--
> lib/libf2fs_zoned.c | 21 +++++++++++++--------
> 2 files changed, 17 insertions(+), 10 deletions(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2022-06-15 16:58 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
[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 ` Jaegeuk Kim [this message]
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=YqoPmgP5DbkXpMmh@google.com \
--to=jaegeuk@kernel.org \
--cc=bvanassche@acm.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.