From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Carlos Maiolino <cem@kernel.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: remove some EXPERIMENTAL warnings
Date: Tue, 13 May 2025 09:07:09 +1000 [thread overview]
Message-ID: <aCJ_HTLLV7zoAYQ-@dread.disaster.area> (raw)
In-Reply-To: <20250510155301.GC2701446@frogsfrogsfrogs>
On Sat, May 10, 2025 at 08:53:01AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Online fsck was finished a year ago, in Linux 6.10. The exchange-range
> syscall and parent pointers were merged in the same cycle. None of
> these have encountered any serious errors in the year that they've been
> in the kernel (or the many many years they've been under development) so
> let's drop the shouty warnings.
>
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
Seems reasonable to me. I haven't encountered any problems with them
over the past few months, so no objections here.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2025-05-12 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lwf6FP6bvClFnnDLscr2Wzt31ZMf-v2JtA-UvFrZWuq8doDoxgvYr6yRjjkRSUbKQ9AH1SQH_9Zar2yIALzAUA==@protonmail.internalid>
2025-05-10 15:53 ` [PATCH] xfs: remove some EXPERIMENTAL warnings Darrick J. Wong
2025-05-12 4:34 ` Christoph Hellwig
2025-05-12 15:14 ` Darrick J. Wong
2025-05-12 15:24 ` Christoph Hellwig
2025-05-12 23:07 ` Dave Chinner [this message]
2025-05-13 8:49 ` Carlos Maiolino
2025-05-13 17:38 ` Carlos Maiolino
2025-05-13 18:50 ` Darrick J. Wong
2025-05-14 7:05 ` Carlos Maiolino
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=aCJ_HTLLV7zoAYQ-@dread.disaster.area \
--to=david@fromorbit.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@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.