From: Markus Elfring via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: masonzhang.linuxer@gmail.com,
linux-f2fs-devel@lists.sourceforge.net, Chao Yu <chao@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add error checking in do_write_page()
Date: Thu, 31 Jul 2025 20:15:19 +0200 [thread overview]
Message-ID: <6bf76f9d-dda4-424b-a0ee-a03547ed5b86@web.de> (raw)
In-Reply-To: <20250731151917.24800-1-masonzhang.linuxer@gmail.com>
> Otherwise, the filesystem may unaware of potential file corruption.
I find that the change description should be improved considerably.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n45
Regards,
Markus
_______________________________________________
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:[~2025-07-31 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 15:19 [f2fs-dev] [PATCH v3] f2fs: add error checking in do_write_page() mason.zhang
2025-07-31 18:15 ` Markus Elfring via Linux-f2fs-devel [this message]
2025-08-01 3:30 ` Chao Yu via Linux-f2fs-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=6bf76f9d-dda4-424b-a0ee-a03547ed5b86@web.de \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=Markus.Elfring@web.de \
--cc=chao@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masonzhang.linuxer@gmail.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).