From: "Theodore Ts'o" <tytso@mit.edu>
To: chuguangqing <chuguangqing@inspur.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ext4: add FALLOC_FL_ALLOCATE_RANGE to supported flags mask
Date: Tue, 15 Jul 2025 08:34:54 -0400 [thread overview]
Message-ID: <20250715123454.GD74698@mit.edu> (raw)
In-Reply-To: <20250715064536.12053-1-chuguangqing@inspur.com>
On Tue, Jul 15, 2025 at 02:45:18PM +0800, chuguangqing wrote:
> Note that since FALLOC_FL_ALLOCATE_RANGE is defined as 0x00, this addition
> has no functional modifications.
>
> Signed-off-by: chuguangqing <chuguangqing@inspur.com>
I'll note that this isn't something which any of the other file
systems (btrfs, xfs, etc.) is doing.
- Ted
next prev parent reply other threads:[~2025-07-15 12:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 3:15 [PATCH 0/1] ext4: add FALLOC_FL_ALLOCATE_RANGE to supported flags mask chuguangqing
2025-07-15 3:15 ` [PATCH 1/1] Add FALLOC_FL_ALLOCATE_RANGE to the set of supported fallocate mode flags. This change improves code clarity and maintains by explicitly showing this flag in the " chuguangqing
2025-07-15 14:08 ` kernel test robot
2025-07-15 4:37 ` [PATCH 0/1] ext4: add FALLOC_FL_ALLOCATE_RANGE to " chuguangqing
2025-07-15 4:37 ` [PATCH 1/1] " chuguangqing
2025-07-15 6:45 ` chuguangqing
2025-07-15 12:34 ` Theodore Ts'o [this message]
2025-07-16 2:28 ` [PATCH v2 0/1] " chuguangqing
2025-07-16 2:28 ` [PATCH v2 1/1] " chuguangqing
2025-07-16 2:44 ` Re: [PATCH " chuguangqing
2025-07-15 12:50 ` Zhang Yi
2025-07-16 3:04 ` [PATCH v3 0/1] Re: " chuguangqing
2025-07-16 3:04 ` [PATCH v3] " chuguangqing
2025-07-16 7:05 ` Zhang Yi
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=20250715123454.GD74698@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=chuguangqing@inspur.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.