From: Markus Elfring <Markus.Elfring@web.de>
To: Baokun Li <libaokun1@huawei.com>, linux-ext4@vger.kernel.org
Cc: yi.zhang@huawei.com, LKML <linux-kernel@vger.kernel.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
Yang Erkun <yangerkun@huawei.com>
Subject: Re: [PATCH 1/5] ext4: replace opencoded ext4_end_io_end() in ext4_put_io_end()
Date: Fri, 20 Dec 2024 11:22:55 +0100 [thread overview]
Message-ID: <12e75d9d-1706-4ee8-b0b8-98a971d6534e@web.de> (raw)
In-Reply-To: <20241220060757.1781418-2-libaokun@huaweicloud.com>
> This reduces duplicate code and ensures that a “potential data loss”
> warning is available if the unwritten conversion fails.
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.13-rc3#n94
Regards,
Markus
next prev parent reply other threads:[~2024-12-20 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 6:07 [PATCH 0/5] ext4: fix issues caused by data write-back failures libaokun
2024-12-20 6:07 ` [PATCH 1/5] ext4: replace opencoded ext4_end_io_end() in ext4_put_io_end() libaokun
2024-12-20 10:22 ` Markus Elfring [this message]
2024-12-20 10:26 ` Jan Kara
2024-12-20 6:07 ` [PATCH 2/5] ext4: do not convert the unwritten extents if data writeback fails libaokun
2024-12-20 10:28 ` Jan Kara
2024-12-20 6:07 ` [PATCH 3/5] ext4: abort journal on data writeback failure if in data_err=abort mode libaokun
2024-12-20 10:36 ` Jan Kara
2024-12-20 13:39 ` Baokun Li
2025-01-06 14:32 ` Jan Kara
2025-01-08 3:43 ` Baokun Li
2025-01-08 13:43 ` Jan Kara
2025-01-08 14:44 ` Baokun Li
2025-01-08 15:28 ` Jan Kara
2025-01-09 2:45 ` Baokun Li
2024-12-20 6:07 ` [PATCH 4/5] ext4: remove unused member 'i_unwritten' from 'ext4_inode_info' libaokun
2024-12-20 11:05 ` Jan Kara
2024-12-20 6:07 ` [PATCH 5/5] ext4: pack holes in ext4_inode_info libaokun
2024-12-20 11:06 ` Jan Kara
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=12e75d9d-1706-4ee8-b0b8-98a971d6534e@web.de \
--to=markus.elfring@web.de \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@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