All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Carlos Maiolino <cem@kernel.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: remove some EXPERIMENTAL warnings
Date: Mon, 12 May 2025 08:14:30 -0700	[thread overview]
Message-ID: <20250512151430.GF2701446@frogsfrogsfrogs> (raw)
In-Reply-To: <aCF6UHNzRqZaH2dK@infradead.org>

On Sun, May 11, 2025 at 09:34:24PM -0700, Christoph Hellwig wrote:
> 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.
> 
> Looks good.  Talking about experimental warnings, I'd also like to
> drop the pnfs warning.  The code has been around forever, and while
> we found occasional issues in the nfsd side of it, they were quickly
> fixed.

I agree, let's drop the pnfs warning since warts or not the code has
been stable for a long time.  However, would you (hch) mind writing that
patch since you're the author of xfs_pnfs.c and I've never even used it.

--D

  reply	other threads:[~2025-05-12 15:14 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 [this message]
2025-05-12 15:24       ` Christoph Hellwig
2025-05-12 23:07   ` Dave Chinner
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=20250512151430.GF2701446@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@infradead.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.