From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Ritesh Harjani <ritesh.list@gmail.com>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2 0/2] Document handing of unwritten bh in ext4_block_zero_page_range()
Date: Mon, 8 Jan 2024 21:53:20 -0500 [thread overview]
Message-ID: <170476879010.637731.8229125857073324497.b4-ty@mit.edu> (raw)
In-Reply-To: <cover.1698856309.git.ojaswin@linux.ibm.com>
On Wed, 01 Nov 2023 22:08:09 +0530, Ojaswin Mujoo wrote:
> ** Changes v1 -> v2 **
>
> * Instead of exiting early in ext4_block_zero_page_range() for unwrit
> bhs like in v1, lets let the current logic be as it is and instead
> document the handing of unwritten buffer heads to make the intent
> clear
>
> [...]
Applied, thanks!
[1/2] ext4: treat end of range as exclusive in ext4_zero_range()
commit: 92573369144f40397e8514440afdf59f24905b40
[2/2] ext4: Clarify handling of unwritten bh in __ext4_block_zero_page_range()
commit: c6bfd724098457a1162a7b9fef07af176720055b
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2024-01-09 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:38 [PATCH v2 0/2] Document handing of unwritten bh in ext4_block_zero_page_range() Ojaswin Mujoo
2023-11-01 16:38 ` [PATCH v2 1/2] ext4: treat end of range as exclusive in ext4_zero_range() Ojaswin Mujoo
2023-11-02 10:08 ` Jan Kara
2023-11-01 16:38 ` [PATCH v2 2/2] ext4: Clarify handling of unwritten bh in __ext4_block_zero_page_range() Ojaswin Mujoo
2023-11-02 10:08 ` Jan Kara
2024-01-09 2:53 ` Theodore Ts'o [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=170476879010.637731.8229125857073324497.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@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